[07:54] <oSoMoN> jibel, what’s the plan with silo 31? will it be validated (again) today?
[08:04] <jibel> oSoMoN, oh, is it ready. I'll do it now
[08:04] <oSoMoN> jibel, thanks!
[08:04] <jibel> I hate where silos are marked ready but are not
[08:04] <jibel> it creates lot of confusion
[08:12] <oSoMoN> me too
[08:12] <oSoMoN> jibel, wouldn’t it be possible to detect when a silo that had previously been marked ready for QA (and had thus generated a trello card in the QA queue) is being rebuilt, and delete that card automatically?
[08:19] <jibel> oSoMoN, it's definitely possible. Just needs the time to do it
[08:19] <jibel> oSoMoN, but really I'd like to get rid of the trello board and integrate it directly into bileto
[08:19] <oSoMoN> ack, so many things to do and so little time/manpower…
[08:20] <oSoMoN> jibel, that’d be even better, indeed
[08:20] <oSoMoN> jibel, is there a bug report I can subscribe to, to track that?
[08:20] <jibel> oSoMoN, no there is none
[08:20] <jibel> and no place to report
[08:20] <jibel> oSoMoN, 31 approved
[08:21] <jibel> oSoMoN, it's a change in 1 statement and covered by a test
[08:21] <oSoMoN> jibel, thanks, I’ve seen and triggered the publication already
[14:52] <pitti> jibel: bonjour jibel, ça va ?
[14:53] <pitti> jibel: is it right that https://platform-qa-jenkins.ubuntu.com/job/ubuntu-xenial-desktop-i386-smoke-default/  is one of the tests that controls the /pending → /current promotion?
[14:53] <jibel> Salut pitti! ça va bien et toi?
[14:53] <pitti> jibel: je vais bien aussi, merci !
[14:53] <jibel> pitti, yes it is
[14:53] <pitti> jibel: I was told that yesterday /current was Apr 1, now it's Apr 5, that seems to match
[14:53] <jibel> pitti, there is a problem with sshd which doesn't start on first boot
[14:53] <pitti> jibel: ok, two questions
[14:53] <jibel> cyphermox was looking into it AFAIK
[14:54] <pitti> I don't see any useful log in https://platform-qa-jenkins.ubuntu.com/job/ubuntu-xenial-desktop-i386-smoke-default/84/ which shows the actual problem
[14:54] <pitti> and are there any kind of email notifications if a test flips from pass to fail?
[14:54] <pitti> I figure watching a dashboard with 100 tests every day isn't practical
[14:54] <cyphermox> that failure is in the test harness
[14:55] <jibel> cyphermox, the problme with ssh?
[14:55] <cyphermox> ie utah is broken, not the image.
[14:55] <cyphermox> jibel: not sure if that was ssh, but permission errors?
[14:55] <cyphermox> oh,
[14:55] <jibel> it works on server and it works if oem is enabled
[14:55] <cyphermox> or network
[14:55] <cyphermox> 2016-04-06 05:28:19,334 root WARNING: Command (ping -c1 -w5 utah-12106-xenial-i386) failed with return code: 1
[14:55] <cyphermox> 2016-04-06 05:41:19,750 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/var/lib/utah/vm/utah-12106-xenial-i386/disk0.qcow2'
[14:55] <cyphermox> 2016-04-06 05:41:19,750 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/var/lib/utah/vm/utah-12106-xenial-i386/tmpC7kDFJ/initrd.lz'
[14:55] <cyphermox> 2016-04-06 05:41:19,751 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/var/lib/utah/vm/utah-12106-xenial-i386/tmpC7kDFJ/xenial-desktop-i386.iso'
[14:55] <pitti> https://platform-qa-jenkins.ubuntu.com/job/ubuntu-xenial-desktop-i386-smoke-default/84/artifact/log/utah-server-ssh.log looks like ssh failure, indeed
[14:55] <cyphermox> 2016-04-06 05:41:19,751 cleanup WARNING: OSError when changing directory permissions: [Errno 1] Operation not permitted: '/var/lib/utah/vm/utah-12106-xenial-i386/tmpC7kDFJ/kernel'
[14:55] <cyphermox> UTAH timeout: retry(sshcheck, retry_timeout=180, logmethod=debug) timed out after 600 seconds
[14:56] <jibel> nuclearbob, ^
[14:56] <pitti> max filed bug 1554266 about that, but so far without reproduction instructions
[14:56] <ubot5`> bug 1554266 in openssh (Ubuntu) "sshd does not start on newly installed desktop system" [Undecided,New] https://launchpad.net/bugs/1554266
[14:56] <cyphermox> ssh works after install, I tried before
[14:56] <pitti> I wasn't able to reproduce that on a cloud or desktop installation so far, so I guess it's related to preseeding or whatnot
[14:57] <pitti> jibel: do you know if someone is watching these failures? I. e. would we know if it fails to promote /current for more than a few days?
[14:57] <cyphermox> pitti: well, I tried preseeding too
[14:57] <cyphermox> pitti: I also gave max an alternate way to install openssh, to see if that made any difference (not that it would)
[14:57] <cyphermox> pitti: I look every once in a while at whether things have migrated :/
[16:40] <jibel> pitti, sorry was in a meeting. The desktop team is supposed to watch those tests
[16:41] <jibel> nuclearbob, ^  can you provide steps to reproduce and did you try the alternate way cyphermox recommended?
[17:55] <nuclearbob> jibel, cyphermox, pitti: I'm watching the tests and making sure we get promotions. I'll add my reproduction steps to the bug, and I'm in the process of trying the alternate method