[13:54] <mup> Bug #1434559 was opened: If node fails to access the image stream, a nasty error log is shown as a notification on teh webui <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1434559>
[14:40] <jrwren> http://askubuntu.com/questions/599157/using-juju-with-maas-worked-at-first-but-is-now-giving-503-error-gomaasapi
[14:43] <kiko> jrwren, we'll need to see what's happening in the maas logs, and also, what the maas version is
[14:43] <kiko> jrwren, so look for tracebacks in /var/log/maas/*.log
[14:43] <kiko> and include the dpkg -l | grep maas output
[14:44] <jrwren> kiko: I think I found the issue. I'll answer my own question in a bit :)
[14:44] <kiko> heh
[14:46] <AskUbuntu_> Using juju with maas worked at first but is now giving 503 error gomaasapi | http://askubuntu.com/q/599157
[15:30] <mup> Bug #1434602 was opened: race condition in maas-region-controller postinst <MAAS:New> <https://launchpad.net/bugs/1434602>
[15:42] <mup> Bug #1434602 changed: race condition in maas-region-controller postinst <MAAS:New> <https://launchpad.net/bugs/1434602>
[15:54] <mup> Bug #1434602 was opened: race condition in maas-region-controller postinst <MAAS:New> <https://launchpad.net/bugs/1434602>
[17:12] <ali8> Does MaaS 1.7.1 support booting from UEFI?
[17:13] <ali8> I'm trying to get it to work at the moment and the node stops at grub
[17:14] <ali8> I'm assuming it's looking for grub.cfg-default-amd64 since grub.cfg includes it, but I don't see that file anywhere on the maas server
[17:21] <kiko> ali8, yes, it definitely does
[17:21] <kiko> blake_r, ^^
[17:22] <kiko> ali8, if you don't get an answer could you ask the question on askubuntu and I'll get somebody to answer?
[17:22] <blake_r> ali8: that file is not on the server
[17:22] <blake_r> ali8: that file is dyanmically generated by the maas tftp server
[17:22] <blake_r> ali8: that alerts MAAS that the machine trying to boot is amd64
[17:23] <blake_r> ali8: at what point in the grub boot does it get?
[17:25] <mup> Bug #1433742 changed: [API] acquiring a node in specific zone doesnt work <MAAS:Invalid> <https://launchpad.net/bugs/1433742>
[17:35] <ali8> hi blake_r, it just shows a grub screen without any options
[17:36] <ali8> thanks kiko, I will
[17:36] <blake_r> ali8: is it the grub command prompt?
[17:37] <ali8> so should I see a request is pserv.log for a grub.cfg-default-amd64? I see a request for bootx64.efi followed by grubx64.efi but nothing else (actually including just grub.cfg)
[17:38] <ali8> yes, it's the grub command prompt
[17:38] <ali8> I also experienced the same issues as described in https://bugs.launchpad.net/maas/+bug/1317705 and patched python-tx-tfp to get around it
[17:40] <blake_r> ali8: what version of ubuntu is your MAAS server?
[17:40] <blake_r> ali8: you should see a request for grub.cfg, then another request for grub.cfg-default-amd64
[17:43] <mup> Bug #1433742 was opened: [API] acquiring a node in specific zone doesnt work <MAAS:Invalid> <https://launchpad.net/bugs/1433742>
[17:43] <ali8> the server is running 14.04, the version of maas installed is  1.7.1+bzr3341-0ubuntu1~trusty1
[17:43] <ali8> maas is from the ppa:maas-maintainers/stable repository
[17:44] <blake_r> do you see those request in clusterd.log
[17:46] <ali8> blake_r: nope... there is almost nothing is cluster.log
[17:46] <ali8> maas-clustured.log
[17:47] <blake_r> ali8: are you seeing any TFTP requests?
[17:47] <kiko> weird
[17:49] <mup> Bug #1433742 changed: [API] acquiring a node in specific zone doesnt work <MAAS:Invalid> <https://launchpad.net/bugs/1433742>
[17:50] <ali8> blake_r: is maas-clustered.log? nope. they are in pserv.log (bootx64.efi, grubx64.efi)
[17:50] <blake_r> ali8: this was an upgrade?
[17:50] <blake_r> ali8: from 1.5?
[17:51] <ali8> blake_r: I ended up purging the old packages and then installing 1.7.1
[17:52] <blake_r> ali8: is the timestamp from pserv.log recent?
[17:54] <ali8> blake_r: yes, it's an hour old, but that is when I ran into this issue. let me just reboot the system again and watch the log
[17:57] <ali8> blake_r:  yes, the pserv.log again shows an access for bootx64 and grubx64 and no other ones
[18:43] <mup> Bug #1431984 changed: [API] acquire does not allow for name= <MAAS:Invalid> <https://launchpad.net/bugs/1431984>
[18:43] <mup> Bug #1434664 was opened: A bulk change of 1000 node statuses will result in 1000 updates to DNS <dns> <scaling> <MAAS:Triaged> <https://launchpad.net/bugs/1434664>
[19:28] <mup> Bug #1434679 was opened: maas does not know about vivid <amd64> <apport-bug> <third-party-packages> <trusty> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1434679>
[20:52] <mup> Bug #1434709 was opened: Node failed to successfully commission <MAAS:New> <https://launchpad.net/bugs/1434709>
[21:13] <mup> Bug #1434709 changed: Node failed to successfully commission <MAAS:New> <https://launchpad.net/bugs/1434709>
[21:19] <mup> Bug #1434709 was opened: Node failed to successfully commission <MAAS:New> <https://launchpad.net/bugs/1434709>
=== jfarschman is now known as MilesDenver
[23:02] <mup> Bug #1434736 was opened: Bulk actions fail altogether (nothing happens) if too many machines are selected <MAAS:Confirmed> <https://launchpad.net/bugs/1434736>