=== chihchun_afk is now known as chihchun | ||
=== chihchun is now known as chihchun_afk | ||
fgimenez | good morning | 07:05 |
---|---|---|
dholbach | good morning | 07:09 |
mvo | ogra_: good morning, it looks like we have dnsmasq and tss both with uid 109 in the image right now, could you have a look please? in wily, not sure about stable, just noticed on wily | 07:10 |
mvo | hey dholbach | 07:10 |
mvo | fgimenez: good morning | 07:10 |
dholbach | hey mvo | 07:10 |
fgimenez | hey mvo, dholbach :) mvo, do we have a rc image? | 07:11 |
mvo | fgimenez: not yet, sorry, I'm working on it now, Chipaca almost fixed the network bug (which is great) | 07:11 |
fgimenez | mvo, awesome! ok np | 07:12 |
dholbach | hola fgimenez :) | 07:12 |
davidcalle | Morning o/ | 07:15 |
clobrano | buongiorno :) | 07:51 |
=== chihchun_afk is now known as chihchun | ||
JamesTait | Good morning all; happy Thursday, and happy Wily Werewolf welease day! 😃 | 08:35 |
dasjoe | JamesTait always seems like the most enthusiastic morning person | 08:42 |
JamesTait | It's all a charade. I'm a grumpy old curmudgeon really. 😉 | 08:47 |
Chipaca | mvo: do you have a branch of almost-next-15.04? | 08:59 |
mvo | Chipaca: 15.04 is up-to-date for the release, I think the one outstanding issue is the ordering | 09:00 |
Chipaca | mvo: and is the latest edge built on that? | 09:00 |
Chipaca | just to minimise the delta i'm working with | 09:00 |
mvo | Chipaca: yes, well, I can build a new image now | 09:00 |
Chipaca | mvo: i mean, will u-d-f build it with that | 09:01 |
Chipaca | or is that what you offered to build? | 09:01 |
mvo | Chipaca: biulding a new amd64 15.04/edge image with todays lp:snappy/15.04 branch so that you have something super close to the stable release | 09:01 |
mvo | Chipaca: does that help you? | 09:01 |
Chipaca | mvo: indeedly it does :) | 09:02 |
Chipaca | and i'll branch that and propose a branch on that | 09:02 |
mvo | Chipaca: thanks, you can also work on trunk right now, we have no delta and I inspected the changes (of course) before merging trunk to 15.04 and it looks very sane (famous last words!) | 09:04 |
Chipaca | ah! perfect then | 09:04 |
mvo | Chipaca: I triggered the image build, new 15.04/edge image should be ready in ~30min or so | 09:04 |
mvo | Chipaca: image build | 09:13 |
mvo | Chipaca: now it just needs to get imported | 09:13 |
Chipaca | mvo: it seems there was a 15.04/edge built overnight | 09:14 |
Chipaca | mvo: working with that for now | 09:14 |
mvo | yeah | 09:14 |
mvo | sure, that will be fine as well, the delta is small | 09:14 |
ogra_ | mvo, whats bad about that ? (tss) | 09:18 |
ogra_ | and yes, i seeded nss3 for a test because it showed up on some list from olli | 09:18 |
mvo | ogra_: two usernames with the same uids | 09:18 |
ogra_ | uh ? | 09:18 |
ogra_ | thats not possible | 09:18 |
mvo | ogra_: yeah, olli asked me to revert that seeding and he said he will follow up | 09:19 |
mvo | ogra_: let me double check about the uid, maybe its something local | 09:19 |
ogra_ | right, as i said, it was for testing (and obviously worth it :) ) | 09:19 |
ogra_ | /etc/passwd is readonly | 09:19 |
ogra_ | and checked during build | 09:19 |
ogra_ | argh | 09:20 |
ogra_ | so no, tss is a requirement for the rootfs encryption stuff | 09:21 |
ogra_ | not related to my nss3 seeding | 09:21 |
ogra_ | and yes, seems thats my bug :( | 09:21 |
ogra_ | (didnt check enough that the tss uid is not already there) | 09:21 |
* ogra_ bumps the UID to 110 | 09:22 | |
mvo | ogra_: thanks, no worries. is this 15.04 too? | 09:25 |
ogra_ | yes | 09:25 |
ogra_ | well, let me check :P | 09:25 |
mvo | ok, please let me know once the fix is upload and I trigger a new amd64 image | 09:26 |
mvo | there is also a fix from Chipaca pending, so no worries we are not golden anyway yet :) | 09:26 |
ogra_ | mvo, not in stable .... phew | 09:27 |
mvo | yay | 09:27 |
ogra_ | now i wonder why we dont have dnsmasq there | 09:28 |
ogra_ | oh, because ubuntu-fan only landed in rolling back then | 09:28 |
ogra_ | (on purpose) | 09:28 |
ogra_ | that was before all the crazy reqs. came in, we shoudl ask if we need fan on stable too now | 09:28 |
ogra_ | uploaded to the PPA | 09:33 |
Chipaca | https://code.launchpad.net/~chipaca/snappy/firstboot-ordering/+merge/275244 is ready for review gents | 09:33 |
Chipaca | fgimenez: if you could try this ^ wrt firstboot bringing up eth0, that'd be cool | 09:34 |
fgimenez | Chipaca, ok on it | 09:38 |
Chipaca | fgimenez: much appreciated! | 09:39 |
Chipaca | fgimenez: i've fake-firstbooted ~20 times and it worked every time, fwiw | 09:40 |
ogra_ | would be nice to know if this by chance also fixes the BBB | 09:44 |
ogra_ | seems racy enough to be possible :) | 09:44 |
ogra_ | /join #ubuntu-release-party | 09:46 |
ogra_ | oops :P | 09:46 |
mvo | Chipaca: \o/ once you fix lands we should have a golden image | 09:56 |
Chipaca | ogra_: this should be less racy than before | 10:04 |
Chipaca | ogra_: so maybe :) | 10:04 |
fgimenez | Chipaca, works great on kvm \o/ | 10:09 |
mvo | Chipaca: (I said it before, but I say it again) \o/ | 10:10 |
Chipaca | fgimenez: and ... bbb? :) | 10:11 |
fgimenez | Chipaca, ogra i'll try bbb now | 10:11 |
Chipaca | whee :) | 10:11 |
fgimenez | Chipaca, yep :) | 10:11 |
Chipaca | fgimenez: could you put a +1 on the branch based on the success of kvm tests? | 10:14 |
fgimenez | Chipaca, sure | 10:14 |
Chipaca | fgimenez: even if it doesn't fix bbb, it fixes amd64, so we can build/release that at least | 10:15 |
fgimenez | Chipaca, there's one error in the test suite on kvm, but not related to eth0 on first boot "Error: open /etc/default/watchdog.wvUpOFylUogg: read-only file system" | 10:21 |
Chipaca | hm! | 10:21 |
Chipaca | eeeep | 10:22 |
Chipaca | ogra_: you around? | 10:22 |
Chipaca | mvo: this might be bad | 10:22 |
ogra_ | what ?!? | 10:22 |
Chipaca | ogra_: we have just /etc/default/watchdog as rw, not the directory itself? | 10:22 |
ogra_ | wh would anything write to it on boot ? | 10:22 |
Chipaca | not boot, this is the integration test suite | 10:23 |
Chipaca | testing setting watchdog | 10:23 |
ogra_ | yeah, makin the directory writable would kind of defeat the purpose | 10:23 |
mvo | uh, atomicWrite ? | 10:23 |
ogra_ | yeah | 10:23 |
ogra_ | needs special hacks | 10:23 |
ogra_ | (like hostname) | 10:23 |
Chipaca | mvo: yes | 10:23 |
mvo | bäää | 10:23 |
ogra_ | yup | 10:23 |
Chipaca | mea culpa, i broke that | 10:24 |
mvo | well, its the right thing to do :/ | 10:24 |
ogra_ | oh is that a function you control (doing the atomic write ?= | 10:24 |
Chipaca | yes | 10:24 |
Chipaca | well | 10:24 |
Chipaca | ogra_: it used to not do an atomic write at all | 10:25 |
Chipaca | ogra_: not even a sync | 10:25 |
Chipaca | maybe the right thing to do is to edit it in writable? | 10:25 |
ogra_ | well, if we want to keep it we need to handle the file like the others in /etc/writable | 10:25 |
Chipaca | would that work? | 10:25 |
ogra_ | i.e. copy it over at image build time and create a link | 10:25 |
Chipaca | i meant edit /writable/system-data/etc/default/watchdog directly | 10:27 |
Chipaca | mvo: ogra_: would editing that directly, from snappy config, be reasonable? | 10:27 |
Chipaca | and would the rename work with the mount | 10:28 |
Chipaca | augh | 10:28 |
Chipaca | mvo: or i just revert the atomicwrite | 10:28 |
Chipaca | and we think about what we've done | 10:28 |
mvo | Chipaca: directly editing /w/s-d/e/d/watchdog would work indeed | 10:29 |
mvo | Chipaca: lets do that for now, we need to re-investigate the writable paths system anyway before 16.04 | 10:30 |
Chipaca | mvo: i'm not sure it'll work | 10:32 |
ogra_ | mvo, Chipaca http://paste.ubuntu.com/12893223/ | 10:32 |
ogra_ | that should work | 10:32 |
* Chipaca hugs ogra_ | 10:32 | |
ogra_ | i assume we want that in stable too ? | 10:33 |
Chipaca | mvo: editing it in /writable doesn't work because the file is the thing mounted, by inode. New file -> new inode | 10:33 |
Chipaca | mvo: afacit at least | 10:33 |
mvo | ogra_: thanks | 10:33 |
mvo | Chipaca: uh, you are right of course | 10:33 |
Chipaca | ogra_: let me check the others i switched over to atomic, just in case | 10:34 |
ogra_ | well, it would work if you made the whole dir writable ... but that means all /etc/default files become writable which isnt so great | 10:34 |
Chipaca | ogra_: the timezone file, the network files (interfaces and pp), the modprobe file, the modules-load file, the watchdog file, and the hostname file | 10:36 |
ogra_ | intefaces has the whole dir writable | 10:36 |
ogra_ | modprobe stuff too | 10:36 |
Chipaca | mvo: we still need a branch for this | 10:37 |
ogra_ | hostname and timezone are already handled | 10:37 |
Chipaca | mvo: (on it) | 10:37 |
ogra_ | so we shoudl eb fie | 10:37 |
ogra_ | *shouold be | 10:37 |
Chipaca | ogra_: but the timezone file is not written to /etc/writable | 10:38 |
ogra_ | (RaspberryPi2)ubuntu@localhost:~$ ls /etc/writable/ | 10:38 |
ogra_ | hostname localtime timezone | 10:38 |
ogra_ | my install disagrees :) | 10:38 |
ogra_ | (RaspberryPi2)ubuntu@localhost:~$ ls -lh /etc/timezone | 10:39 |
ogra_ | lrwxrwxrwx 1 root root 17 Jul 24 16:36 /etc/timezone -> writable/timezone | 10:39 |
Chipaca | ogra_: yes, but when you set it, it's written to /etc/timezone directly | 10:39 |
ogra_ | which is a link | 10:39 |
Chipaca | ogra_: which means the atomic code will try to create /etc/timezone.somecrap | 10:39 |
ogra_ | no, it should do the atomic write in /etc/writable | 10:40 |
ogra_ | (this is why we have that dir at all :) ) | 10:40 |
Chipaca | ogra_: what about localtime? | 10:40 |
ogra_ | we should have called it /etc/atomic insztead, to make the purpose more clear ;) | 10:40 |
ogra_ | same thing | 10:40 |
ogra_ | as well as hostname | 10:40 |
Chipaca | ogra_: and watchdog.conf | 10:41 |
ogra_ | the filesystem takes care here | 10:41 |
ogra_ | ah, not only the /etc/default/watchdog file ? | 10:41 |
ogra_ | ok, adding | 10:41 |
Chipaca | ogra_: i think that covers it | 10:42 |
ogra_ | good | 10:42 |
ogra_ | uploaded to the PPA for wily ... now doing stable | 10:43 |
Chipaca | mvo: https://code.launchpad.net/~chipaca/snappy/use-etc-writable-for-atomics/+merge/275302 | 10:45 |
mvo | Chipaca: thanks | 10:46 |
ogra_ | stable uploaded too | 10:47 |
mvo | ogra_: \o/ | 10:47 |
Chipaca | interesting that the bbb tests caught this and not the kvm ones | 10:48 |
ogra_ | http://themcphails.uk/snappy.jpg | 10:48 |
ogra_ | :) | 10:49 |
ogra_ | Chipaca, errr | 10:49 |
ogra_ | no | 10:49 |
Chipaca | ogra_: no? | 10:50 |
ogra_ | you want to edit the original places | 10:50 |
ogra_ | the filesystem should care for the rest | 10:50 |
ogra_ | dont edit in /etc/writable | 10:50 |
Chipaca | ogra_: buh.. buh... ? | 10:50 |
ogra_ | your atomic write should follow the link before doing the backup copy | 10:51 |
ogra_ | and the filesystem should manage that for you, so there should eb no need to touch /etc/writable directly | 10:51 |
Chipaca | siiigh | 10:52 |
mvo | Chipaca, ogra_: I'm not sure if our code is doing that, I think it would replace the link (but thats from memory only) | 10:52 |
ogra_ | (at least all other writin tools do it like rthat ... this setup comes from the phone where it exists since years ) | 10:52 |
Chipaca | mvo: it isn't, but it should perhaps | 10:52 |
ogra_ | it definitely should | 10:52 |
ogra_ | everythjing else does | 10:52 |
Chipaca | mvo: so, abort, abort, etc | 10:52 |
mvo | done | 10:52 |
Chipaca | mvo: tarmac didn't care and merged it anyway. NEver mind, follow up branch will revert. | 11:09 |
Chipaca | mvo: https://code.launchpad.net/~chipaca/snappy/atomic-follow-symlinks/+merge/275310 | 11:26 |
ogra_ | looks good | 11:28 |
fgimenez | Chipaca, first boot works fine in bbb too, now running the suite | 11:28 |
ogra_ | fgimenez, no mopre missing address ? | 11:29 |
fgimenez | ogra_ iirc that was happening on rolling only, let me check | 11:29 |
ogra_ | it could be the same cause | 11:29 |
fgimenez | ogra_, yes, rolling/edge https://bugs.launchpad.net/snappy/+bug/1503329, i'll try the fix there too | 11:30 |
ubottu | Launchpad bug 1503329 in Snappy "not getting an ipv4 address on the first boot" [Critical,Confirmed] | 11:30 |
ogra_ | fgimenez, though it could also be the double UID (for dnsmasq vs tss) which would be fixed in the next image | 11:31 |
ogra_ | especially if it is rolling only ... only rolling has this UID bug | 11:31 |
=== olli_ is now known as olli | ||
fgimenez | ogra_, ack thanks | 11:36 |
=== chihchun is now known as chihchun_afk | ||
* ogra_ sighs about the RPi devicetree issues :/ | 12:01 | |
ogra_ | mvo, please remind me that we talk about that once the release is out ... ^^^ | 12:02 |
mvo | ogra_: ok | 12:02 |
mvo | Chipaca: thanks! | 12:02 |
Chipaca | augh | 12:14 |
mvo | Chipaca: more crisis? | 12:15 |
mvo | hm, apparently | 12:15 |
Chipaca | mvo: :) | 12:15 |
Chipaca | or :-/ | 12:15 |
Chipaca | depending on the flavour of your cynicism | 12:15 |
* mvo hugs Chipaca | 12:15 | |
mvo | all good | 12:15 |
Chipaca | mvo: there's an explicit test for us not following symlinks there | 12:17 |
mvo | Chipaca: geh | 12:18 |
mvo | Chipaca: let me check that, I wonder why | 12:18 |
mvo | Chipaca: I have some vague memory why this might be useful to not follow symlinks | 12:18 |
Chipaca | mvo: security, usually | 12:18 |
mvo | Chipaca: yeah, I think so, I think it came up as part of the recent click issue | 12:19 |
Chipaca | mvo: for example :) | 12:20 |
mvo | Chipaca: hmmmmmmmmmmmm, so indeed we added this recently as a result of click issue | 12:21 |
Chipaca | yep | 12:21 |
mvo | Chipaca: so lets not merge it and use /etc/writable and look into this after the reelease again | 12:21 |
mvo | Chipaca: its a mess anyway | 12:21 |
mvo | Chipaca: or do you have an alternative suggestion :) ? | 12:22 |
Chipaca | mvo: adding a flags parameter to AtomicWriteFile, which defaults to nofollow | 12:22 |
mvo | Chipaca: even better | 12:23 |
=== matiasb_ is now known as matiasb | ||
Chipaca | mvo: updated lp:~chipaca/snappy/atomic-follow-symlinks if you want to take a look | 12:45 |
mvo | Chipaca: done, thanks again | 12:46 |
mvo | fgimenez: r223 for amd64 is ready, if you could give this a early testrun | 14:00 |
mvo | elopio: -^ | 14:00 |
mvo | I will build arm/i386 too now | 14:00 |
fgimenez | mvo, thanks on it | 14:00 |
mvo | thank you! | 14:00 |
fgimenez | mvo, the watchdog config test is still failing with a different error now "Error: open /etc/default/writable/default: no such file or directory" | 14:16 |
mvo | fgimenez: aha, thanks. let me check | 14:16 |
mvo | Chipaca: -^ | 14:16 |
mvo | or maybe ogra_ ---^ ? | 14:18 |
ogra_ | hrn | 14:18 |
ogra_ | yeah, that might be wrong link ... | 14:19 |
mvo | http://paste.ubuntu.com/12894264/ | 14:19 |
ogra_ | hmm, no, that looks right | 14:19 |
ogra_ | how does /etc/writable look like ? | 14:20 |
mvo | ogra_: http://paste.ubuntu.com/12894275/ | 14:20 |
ogra_ | looks fine too | 14:21 |
mvo | ogra_: that looks right? isn't there a "/" missing in the first one? | 14:21 |
ogra_ | oooh !! | 14:21 |
ogra_ | no | 14:21 |
ogra_ | there would be a ../ missing | 14:21 |
ogra_ | damned | 14:22 |
ogra_ | that needs more logic in livecd-rootfs :/ | 14:22 |
ogra_ | will fix after meeting | 14:23 |
mvo | ta | 14:23 |
elopio | fgimenez: why don't you do a show and tell on the next ubuntu summit? | 14:29 |
fgimenez | elopio, well, i doubt i have anything interesting to show or tell ;) | 14:30 |
elopio | I think it would be cool to show the integration suite on kvm. But maybe the stuff you did on snappy-tests-job, or some other cool thing you liked. | 14:31 |
elopio | fgimenez: it doesn't have to be a full hour. I'd be interested also in things like the api test suite, or the cli one, or the failover tests. | 14:33 |
elopio | balloons: help me out here :) | 14:33 |
fgimenez | elopio, ok i'll have a look, are you going to do something for the summit? | 14:34 |
balloons | fgimenez, definitely! You can demo something for 5-10 mins and take a couple questions. It can be really quick if you wish | 14:34 |
elopio | fgimenez: no. I prefer to help you with yours, if you need a hand. | 14:34 |
ogra_ | mvo, http://paste.ubuntu.com/12894355/ does that look ok to you ? | 14:36 |
mvo | ogra_: yes, thank you | 14:37 |
ogra_ | (assuming we might get more files in /etc/default to be writable one day) | 14:37 |
ogra_ | uploading then | 14:37 |
elopio | fgimenez: any chance you have an old 15.04 edge around? like #142? | 14:37 |
fgimenez | balloons, elopio ok thanks, let's see if there's something interesting enough (or at all :) in all this stuff.. | 14:38 |
fgimenez | elopio, nope, i've seen the bug, maybe from old stables? | 14:38 |
elopio | fgimenez: I'll try re-updates from different stables. If the bug doesn't happen there, then it's not important. | 14:39 |
fgimenez | elopio, sgtm | 14:40 |
elopio | fgimenez: have you confirmed if Chipaca's fix solves the problem? | 14:42 |
fgimenez | elopio, yes, eth0 is up on first boot for both amd64 and bbb, it's already included in r223 | 14:43 |
elopio | cool. Then I'll go and take a walk with the dog while the automated suite runs here. | 14:44 |
fgimenez | elopio, haven't tried it yet on rolling/edge bbb, maybe it solves the ipv4 issue too | 14:44 |
elopio | bbs | 14:44 |
elopio | fgimenez: ah, I'll leave that one flashing and check. | 14:44 |
elopio | fgimenez: hey, btw, I started getting tls handshake timeouts when doing u-d-f. | 14:46 |
elopio | I still think that's a problem in the store servers. Just not sure what to do about it to prove it. | 14:47 |
fgimenez | elopio, from udf too? i think i saw that some time ago, yes, it seems to be a problem of the store | 14:47 |
Chipaca | ogra_: mvo: status update wrt symlinks plz (but no rush) | 14:51 |
ogra_ | Chipaca, fix is in the PPA ... waiting for promotion and new image | 14:51 |
Chipaca | neat-o | 14:52 |
Chipaca | i'll go get myself a cuppa tea then | 14:52 |
kgunn | tedg: hey so, made some good headway last night on the mir yaml, but wondering...at least one of the paths wanted arch specific input, is there a way to late bind that in the yaml ? so it'd insert whatever arch your building on? | 14:52 |
tedg | kgunn: No, I don't think we have anything for that. | 14:53 |
tedg | kgunn: One design floating around had variables, but I don't think they've made it to a final design. | 14:53 |
tedg | kgunn: We need to do some more thinking around cross-building and architectures, we're weak there right now. | 14:53 |
kgunn | tedg: ok..understood | 14:54 |
kgunn | just felt naughty | 14:54 |
tedg | kgunn: In a good way? ;-) | 14:55 |
kgunn | lol | 14:55 |
kgunn | no, most definitely not | 14:56 |
=== ubott2 is now known as ubottu | ||
=== Odd_Blok1 is now known as Odd_Bloke | ||
ogra_ | new stable image building | 15:02 |
ogra_ | fgimenez, elopio ^^^ with a fix for /etc/default/watchdog | 15:02 |
=== moul_ is now known as moul | ||
=== mariogrip_ is now known as mariogrip | ||
=== Ursinha_ is now known as Ursinha | ||
ogra_ | Xenial-changes Subscription results | 15:14 |
ogra_ | Your subscription request has been received, and will soon be acted upon.... | 15:14 |
ogra_ | :D | 15:14 |
=== Chipaca` is now known as Chipaca | ||
=== Tristit1a is now known as Tristitia | ||
elopio | fgimenez: I'm getting an error on the config test: open /etc/default/writable/default: no such file or directory | 15:42 |
ogra_ | elopio, yes, thats is what we are doing the current re-spin for | 15:42 |
ogra_ | 225 should be fixed | 15:43 |
elopio | ogra_: oh, I thought that was already on 225. | 15:43 |
elopio | sorry, on 224 | 15:43 |
ogra_ | aaand ... 225 hit the system-image server this second :) | 15:43 |
ogra_ | so happy testing :) | 15:43 |
elopio | ok good, the tests work :) | 15:43 |
* elopio u-d-fs | 15:43 | |
ogra_ | let me know how it goes ... i *belive* it is fixed ... but religion might not help here ;) | 15:44 |
elopio | I bet religion will just make it worse ;) | 15:45 |
ogra_ | heh, yeah | 15:48 |
fgimenez | elopio, ogra_ it still fails for me "Error: rename /etc/writable/watchdog.conf.HGxhokjLnsKB /etc/writable/watchdog.conf: device or resource busy" | 15:51 |
ogra_ | huh ? | 15:51 |
ogra_ | thats a different file though | 15:51 |
ogra_ | Chipaca, ^^^ did your atomic write fix not land yet ? | 15:52 |
ogra_ | "device or resource busy" is also a very interesting error message here | 15:53 |
elopio | Error: rename /etc/writable/watchdog.conf.elXUoCIALnmQ /etc/writable/watchdog.conf: device or resource busy | 15:53 |
elopio | same here. | 15:53 |
ogra_ | yeah | 15:53 |
ogra_ | so the fix for /etc/default/watchdog works ... | 15:53 |
ogra_ | but we are back at the initial error from this morning | 15:54 |
ogra_ | weird | 15:54 |
ogra_ | i thought Chipaca's fix had landed already | 15:54 |
Chipaca | ogra_: that looks like the one with my fix | 16:05 |
ogra_ | so why do we get that weird error ? | 16:05 |
Chipaca | "device or resource busy" is not the error from this morning | 16:05 |
Chipaca | because | 16:05 |
Chipaca | it's still mounted | 16:05 |
Chipaca | i'd wager | 16:05 |
ogra_ | why would it not be mounted | 16:05 |
Chipaca | ogra_: i mean, we used to mount /etc/watchdog.conf | 16:06 |
ogra_ | ooooh ! | 16:06 |
ogra_ | crap | 16:06 |
Chipaca | oooh. | 16:06 |
Chipaca | :) | 16:06 |
Chipaca | ogra_: only guessing, but that's what i'd look at, myself | 16:06 |
ogra_ | yeah | 16:07 |
ogra_ | nobody updated ubuntu-core-config | 16:07 |
Chipaca | silly nobody | 16:07 |
=== dpm is now known as dpm-afk | ||
ogra_ | uploaded (for vivid yet) | 16:10 |
fgimenez | leaving, good evening o/ | 16:10 |
ogra_ | bah, and i cant land it for wily | 16:12 |
ogra_ | oh, i can | 16:13 |
ogra_ | hah | 16:13 |
ogra_ | ok, wily fix uploaded too | 16:15 |
seb128 | wah, nobody fixed 1.6 so wily released with 1.5? | 16:16 |
ogra_ | seb128, seemingly slipped through, we'Re all super busy doing a release :) | 16:19 |
Chipaca | off to a parents' evening, will bbl | 16:34 |
ogra_ | elopio, 226 building | 16:34 |
elopio | testing 226 now | 17:18 |
ogra_ | yay, thanks | 17:19 |
* ogra_ was about to ping that it is done :) | 17:19 | |
=== charles__ is now known as charles | ||
elopio | ogra_: Chipaca: the test now passes. Trying the rest. | 17:35 |
ogra_ | YAY ! | 17:35 |
* ogra_ relaxes | 17:35 | |
elopio | ogra_: oh, don't relax. I have food for thought for you: how can we put a regression test that doesn't require us to regenerate an image to check it? | 17:37 |
ogra_ | elopio, well, you could replace the changed parts if yu know exactly which are the ones ... but that only works if neither initrd nor firstboot is involved | 17:41 |
ogra_ | (and indeed if it isnt bootloader or kernel stuff) | 17:41 |
ogra_ | in the watchdog case this wouldnt have helped | 17:41 |
elopio | ogra_: where can I see what you changed to fix it? | 17:42 |
ogra_ | usually in the MPs but for certain packages like livecd-rootfs or ubuntu-core-config you can only see it in the package diff of the PPA | 17:42 |
ogra_ | https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages ... if you expand either of the "ubuntu-core-config" packages on that page there is a diff below | 17:43 |
elopio | I see. This is pretty hard, because it's not like an api that snappy consumes. | 17:47 |
ogra_ | yeah, thats plumbing ... | 17:47 |
elopio | ogra_: will this core-config be a snap eventually too? | 17:48 |
ogra_ | what you can definitely look at is http://people.canonical.com/~ogra/core-image-stats/ | 17:48 |
ogra_ | no, its one of the debs we create the rootfs from | 17:48 |
ogra_ | the rootfs will become a snap but not the parts used to build it | 17:48 |
ogra_ | for 226 the changelog is http://people.canonical.com/~ogra/core-image-stats/vivid/20151022.5.changes | 17:49 |
elopio | ogra_: so this goes back to being able to create a rootfs on demand. Once we build it, we can plug it into an existing image and check. | 18:16 |
elopio | not perfect, but will reduce the feedback time. | 18:16 |
ogra_ | elopio, well, why not generate a complete image then ? | 18:36 |
elopio | ogra_: I guess you are right. But we need to isolate the changes as much as possible. | 18:38 |
elopio | maybe we can make a contract between snappy and what ubuntu-core-config produces. And then test just that. | 18:38 |
elopio | anyway, I think that the next step would be to generate a complete image, as you say. | 18:39 |
elopio | ogra_: what's wrong with this? http://pastebin.ubuntu.com/12896455/ | 19:13 |
elopio | I don't understand the error. | 19:13 |
mvo | elopio: hi, so whats the status? how is the imgae looking? | 19:29 |
mvo | ogra_: or you maybe, how is the image looking? | 19:32 |
elopio | mvo: all good with kvm, already a couple of full successful runs + exploring. | 19:35 |
elopio | tests are currently running on bbb and rpi. | 19:35 |
elopio | mvo: I think we are good to publish to alpha to test the upgrade and rollback | 19:36 |
mvo | elopio: excellent, let me do that then | 19:36 |
elopio | mvo: so, will you trigger staging tomorrow? | 19:38 |
elopio | and who should we notify to get the cert team testing alpha? | 19:38 |
mvo | elopio: I can stay up some more to release today, depends a bit how long the test runs will take | 19:39 |
mvo | elopio: and when its stable I will tell the cert guys to use it (thats how we usually do it) | 19:40 |
mvo | elopio: amd64/armhf/i386 ready in alpha | 19:41 |
elopio | mvo: great. I'll download and flash | 19:42 |
mvo | elopio: thanks, just keep me updated, I will be around for ~1h at least, otherwise I will continue (early) in my morning | 19:43 |
ogra_ | mvo, its all fine (like elopio said) ... had to do a re-spin because we forgot to drop the watchdog stuff from ubuntu-core (so it was still bind mounted) | 19:57 |
mvo | ogra_: aha, thanks | 19:58 |
elopio | mvo: tested alpha 14 -> 15, rollback, update again, and then the full suite on kvm | 20:24 |
elopio | the boards in progress. But that's a lot slower. Things look good. | 20:25 |
mvo | elopio: yay, thanks | 20:26 |
elopio | I think last time ricmm told us to notify the chinese team to test the alpha before the release, but I'm not sure about that part of the process. | 20:26 |
mvo | elopio: let me ask | 20:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!