=== shuduo-afk is now known as shuduo === chihchun_afk is now known as chihchun === spineau is now known as spineau_afk === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === tsimonq2alt is now known as tsimonq2 === spineau_afk is now known as spineau [14:14] nuclearbob: hey [14:14] cyphermox: howdy [14:15] I see the mark-pending-current job on platform-qa-jenkins hasn't successfully run in a while [14:15] now, looks like it hasn't been triggered at all in 2 days, but before that it was failing with weird permission errors: [14:16] (well, the underlying jobs did anyway) https://platform-qa-jenkins.ubuntu.com/job/ubuntu-xenial-desktop-amd64-smoke-default/62/console [14:18] I'm guessing it's not getting run at all because there are no executors to run it: https://platform-qa-jenkins.ubuntu.com/job/ubuntu-xenial-desktop-amd64-iso-download/urltriggerPollLog/ [14:19] venonat-desktop-iso is down [14:19] cyphermox, ah right, I restarted it [14:20] cyphermox: we're also not getting any passes on the desktop install right now, I'll find the bug about that [14:20] right, there were two issues [14:21] jibel; I don't have access to do that, but could you add me to emails that may go out if that agent is down? [14:21] cyphermox, we don't receive emails [14:21] or nuclearbob: ^ [14:21] ah [14:22] cyphermox, but given how often they go down we should probably add some [14:22] jibel: I wonder if that's something that could be checked [14:22] what's the name of that thing we use to monitor failures? we use version 3 of it and I'm forgetting right now [14:22] nagios? [14:22] cyphermox, do you know anything about the ubiquity changes that were intended to come at one point this cycle? [14:22] nuclearbob, sounds easy with the API [14:22] nagios, yes [14:23] jibel: okay, I didn't know the api could send emails for nodes being down [14:23] specifically, I mean the proposed design changes, qt rewrite, etc [14:23] yeah, the jenkins API might not be able to notify you for the agents, I'm not sure [14:23] nuclearbob, I mean a nagios check for example that would poll the status of the slaves [14:23] jibel: right, I think that would be quite easy [14:23] nuclearbob, but really it shouldn't be our problem [14:23] jibel: indeed [14:23] balloons: some design changes happened for Secure Boot; qt rewrite I have no idea about [14:24] jibel: whose problem should it be? [14:24] nuclearbob, I4d rather file an rt for plars [14:24] jibel: makes sense to me [14:24] cyphermox, people managing the hardware, in this case the cert team [14:24] oh ok [14:24] cyphermox, ack. Might I also bug you for a review at some point on https://code.launchpad.net/~nskaggs/ubiquity/add-boot-to-installer-ap-test/+merge/288959? It's a new test for the AP ubiquity testing [14:25] balloons: sure. I think I had looked at merges just before but it took some time to get things ready and tested [14:26] balloons: it will have to land when we next have to land ubiquity though, I'm not going to make an upload just for this [14:27] right, no worries. It just needs to hit trunk for Max to make use of it [14:30] balloons: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6392 [14:31] nuclearbob, ^^ :-) [14:31] balloons: all right === chihchun is now known as chihchun_afk === shuduo is now known as shuduo-afk [22:23] nuclearbob: did you find out anything about the image smoketests after all? [22:24] cyphermox: desktop is currently blocked by this bug: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266 [22:24] Launchpad bug 1554266 in openssh (Ubuntu) "sshd does not start on newly installed desktop system" [Undecided,New] [22:25] cyphermox: sshd won't start the first time on a newly rebooted system if it's installed via preseed. It is installed and will be started on a reboot, and can be started manually [22:25] cyphermox: this doesn't affect the server images [22:29] err what? [22:29] that makes no sense [22:31] cyphermox: the problem makes no sense, or it does not make sense for that to block promotions? [22:32] cyphermox: the problem we run into is that we can't run automated tests if ssh never comes up [22:32] yeah [22:33] I'm saying it makes no sense for ssh to behave differently on server than on desktop, or for it to matter whether it was a preseeded install [22:33] (especially not after a reboot) [22:33] yeah [22:33] it's a pretty confusing problem [22:33] but not a difficult one for me to recreate [22:36] please file a bug about it [22:40] do I need to create a new task on the bug I linked? [22:41] oh sorry, I derped. [22:42] no problem :)