[05:29] <pitti> Good morning
[06:59] <pitti> jibel: could it be that the quantal-saucy-* tests on wazn actually use the quantal-trusty-* containers?
[07:36] <pitti> jibel: I'd like to add a grub workaround for bug 1060404, which breaks the quantal → saucy upgrades
[07:37] <pitti> jibel: if I add the workaround to LXC's bootstrap(), is it true that I can just blow away the existing container and the job will regenerate it? certainly looks like it, but I don't know whether you did any customizations to the containers which need to be recreated then
[07:37] <jibel> pitti, Good morning
[07:37] <pitti> bonjour jibel, ça va ?
[07:38] <jibel> pitti, q->s use q-s containers, the profile was misconfigured with trusty as target release, but I fixed it and they should use q-s containers now
[07:38] <jibel> pitti, ça va bien et toi?
[07:39] <jibel> pitti, there is no customization to the containers, you can destroy them and they'll be recreated
[07:39] <pitti> jibel: je n'ai pas domi bien
[07:39] <jibel> pitti, you're training to support jetlag next week ? ;)
[07:39] <pitti> upgrade-tester@wazn:~$ sudo lxc-ls --fancy|grep quantal
[07:39] <pitti> heh
[07:40] <pitti> → only gives me quantal-trusty-*, no quantal-saucy-*
[07:40] <pitti> but http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-quantal-saucy-desktop-amd64/27/consoleText confirms that it was running on wazn
[07:40] <pitti> Testing '/home/upgrade-tester/auto-upgrade-tester/profiles/trusty/ubuntu-quantal-saucy-desktop-amd64'
[07:40] <pitti> profilename:  upgrader-ubuntu-quantal-trusty-desktop-amd64
[07:47] <jibel> pitti, hm, looking
[07:50] <pitti> jibel: so I want to replace /etc/kernel/postinst.d/zz-update-grub if src_release == 'quantal'; I'd need to do that before starting the container, otherwise it would only be in the overlay, right?
[07:52] <jibel> pitti, if you do it in bootstrap() it will be done in the base container
[07:53] <pitti> jibel: ah, you think it's better to always apply it in upgrade()?
[07:55] <jibel> pitti, if the workaround must always be applied for quantal it doesn't hurt to apply it to the base image, does it?
[07:55] <pitti> jibel: no, it doesn't
[07:56] <pitti> jibel: and I don't see that I have rootfs and src_release in upgrade(), so it's easier there, too
[07:56] <pitti> it's modifying a conffile, so we should get a conffile prompt on that; but we can filter that out
[07:57] <pitti> I asked on the bug whether we should SRU it properly, then we can remove this again
[07:59] <jibel> pitti, I fixed profiles q->s to generate a container q-s, the target release was set to trusty, I forgot to commit my changes
[07:59] <pitti> jibel: ah, thanks
[08:00] <pitti> darn, I just started a build 3 seconds ago
[08:00] <pitti> but, there will be more runs :)
[08:00] <jibel> pitti, there is a whitelist for conffiles that are expected
[08:00] <jibel> in the test
[08:01] <pitti> jibel: oh, I don't see that in "share/post_upgrade_tests/test_conffiles.py
[08:02] <pitti> oh, you mean that checks which conffiles were already modified before the upgprade
[08:04] <jibel> pitti, I mean if there is a .dpkg-dist created because the file has been voluntarily modified before the upgrade, it can be ignored.
[08:05] <pitti> jibel: so whatever you changed for q->s, is that in bzr? there are no new commits
[08:06] <pitti> run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.5.0-45-generic /boot/vmlinuz-3.5.0-45-generic
[08:06] <jibel> pitti, in lp:~jibel/+junk/auto-upgrade-testing_profiles/
[08:06] <pitti> disabled to work around LP#1060404
[08:07] <pitti> banzai!
[08:07] <pitti> jibel: ah
[08:07] <jibel> I'll move them back to trunk
[08:07] <pitti> I wonder how bootstrapping the quantal containers worked without that in the first place
[08:07] <jibel> merge them actually
[08:08] <pitti> upgrader-ubuntu-quantal-saucy-server-amd64               RUNNING  10.0.3.45  -     NO
[08:08] <pitti> jibel: ^ confirmed, thanks
[08:24] <jibel> pitti, what's the problem with unity, python-apt,... and python:any in http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-precise-trusty-desktop-i386_vm/25/console
[08:27] <pitti> jibel: filed a while ago as bug 1271237
[08:27] <pitti> jibel: in short, we need to teach apt or u-m to first upgrade dpkg and apt, then the rest
[08:27] <pitti> precise's apt doesn't understand python:any dependencies yet
[08:27] <jibel> pitti, ah right, thanks
[08:28] <pitti> jibel: I have that, bug 1279424, and bug 1060404
[08:28] <pitti> with these fixed, we should have a lot of green
[08:29] <pitti> hm, yesterday we also had that conffile prompt, searching where that was
[08:33] <jibel> pitti, it was precise-trusty-server-tasks IIRC
[08:34] <pitti> hm, building the container got stuck
[09:05] <pitti> jibel: the workaround worked, now I get a conffile failure on that file: http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-quantal-saucy-server-amd64/28/artifact/results/bootstrap.log
[09:06] <pitti> ah, I should probably move the original file to dpkg-dist in teh workaround, so that the "new changed conffile" detection works
[09:07] <pitti> no, I misunderstood that; I'll just whitelist it
[09:07] <jibel> pitti, http://paste.ubuntu.com/6924523/ should be enough
[09:08] <jibel> +/tmp/
[09:08] <pitti> right, that's what I'm doing now
[09:11] <pitti> jibel: http://paste.ubuntu.com/6924537/
[09:11] <jibel> pitti, LGTM
[09:18] <pitti> green!
[10:52] <davmor2> Morning all
[17:31] <balloons> can anyone reach https://wiki.ubuntu.com/QATeam/Roles/Tester?
[17:33] <balloons> so weird, I can't get to it on my mainbox.. wild
[17:34] <mrgoodcat> working fine for me
[17:35] <balloons> ty mrgoodcat :-) Good to know the crazy begins and ends here
[17:36] <mrgoodcat> I know the ubuntu wiki is caps sensitive, could that be your issue?
[17:41] <balloons> well now it's working. I was getting server 400 errors
[17:41]  * balloons rattles head
[17:41] <balloons> good point on the caps sensitive though!
[17:41] <balloons> https vs http as well
[18:00] <mrgoodcat> it is the only caps sensitive website i can remember seeing in a while
[18:01] <mrgoodcat> actually i just tested a few and apparently caps sensitive is normal behaviour and i never noticed
[18:01] <balloons> :-)
[19:13] <hggdh> host names on URLs are not caps-sensitive, but the rest of it will probably be (certain on Unix servers, unknown on Windows ones)
[19:21] <balloons> I'll take the high road on this one and blame, well let's see.. nyan.cat
[19:25] <phillw> balloons: you have mail
[20:49] <balloons> phillw, ty ;-)
[20:50] <phillw> balloons: yvw... I do lurk :)