[00:07] <catbus1> kiko: ^^^
[00:10] <catbus1> wolverineav: it's not 'fix released' so I would expect the bug still exists for 1.8. I think this bug probably should be targeted to 1.8 and 1.9 if the bug is valid for 1.8 and 1.9.
[00:12] <wolverineav> catbus1: ok, that sounds good
[07:24] <mup> Bug #1472116 opened: Juju failed to bootstrap MAAS with 500 INTERNAL SERVER ERROR / unknown error <1.8> <juju> <MAAS:New> <https://launchpad.net/bugs/1472116>
[11:37] <mup> Bug #1472228 opened: maas-pserv still " Stop"  !!  <MAAS:New> <https://launchpad.net/bugs/1472228>
[13:22] <mup> Bug #1472260 opened: MAAS picks wrong cluster-controller for curtin install <MAAS:New> <https://launchpad.net/bugs/1472260>
[13:52] <mup> Bug #1472268 opened: Interface with sticky IP gets prioritized dynamic IP address as well  <MAAS:New> <https://launchpad.net/bugs/1472268>
[14:01] <mup> Bug #1472268 changed: Interface with sticky IP gets prioritized dynamic IP address as well  <MAAS:New> <https://launchpad.net/bugs/1472268>
[14:04] <mup> Bug #1472268 opened: Interface with sticky IP gets prioritized dynamic IP address as well  <MAAS:New> <https://launchpad.net/bugs/1472268>
[15:55] <mup> Bug #1402042 opened: console= parameters need to be added before -- on kernel cmdline <curtin:Confirmed> <MAAS:Triaged> <MAAS 1.7:Triaged> <MAAS trunk:Triaged> <curtin (Ubuntu):Confirmed> <debian-installer-utils (Ubuntu):Fix Released> <maas (Ubuntu):New> <debian-installer-utils (Ubuntu
[15:55] <mup> Precise):New> <maas (Ubuntu Precise):New> <curtin (Ubuntu Trusty):Confirmed> <debian-installer-utils (Ubuntu Trusty):New> <maas (Ubuntu Trusty):New> <curtin (Ubuntu Utopic):Won't Fix> <debian-installer-utils (Ubuntu Utopic):New> <maas (Ubuntu Utopic):New> <curtin (Ubuntu Vivid):Confirmed>
[15:55] <mup> <debian-installer-utils (Ubuntu Vivid):New> <maas (Ubuntu Vivid):New> <curtin (Ubuntu Wily):Confirmed> <debian-installer-utils (Ubuntu Wily):Fix Released> <maas (Ubuntu Wily):New> <Debian:Fix Released> <https://launchpad.net/bugs/1402042>
[16:05] <voidspace> rvba: ping
[16:05] <rvba> voidspace: hi
[16:06] <voidspace> rvba: hey, hi
[16:06] <voidspace> rvba: I'm using the devices API, via gomaasapi, to create a device and then allocate an address for the device
[16:06] <voidspace> rvba: so far so good
[16:06] <voidspace> rvba: when I try to delete the device (on container destruction), via gomaasapi, I get an error 403
[16:07] <rvba> voidspace: 403?  That's odd.
[16:08] <voidspace> rvba: ah, and the error document (html!?) includes: CSRF verification failed. Request aborted
[16:08] <voidspace> rvba: maybe CSRF hasn't been turned off for that api endpoint
[16:09] <voidspace> this is using 1.9 dailybuilds
[16:10] <rvba> voidspace: CSRF should be disabled for the entire API… but let me have a look at the code to be sure…
[16:10] <voidspace> I'm double checking my usage of the api
[16:11] <voidspace> rvba: my fault
[16:11] <rvba> voidspace: ah! :)
[16:11] <voidspace> rvba: I'm using "device" instead of "devices" as the api endpoint
[16:11] <voidspace> interesting error though
[16:11] <rvba> Indeed.
[16:11] <voidspace>  /device/systemId
[16:11] <voidspace> when it should be /devices/systemId/
[16:11] <rvba> Right.
[16:11] <voidspace> rvba: sorry for the noise
[16:11] <rvba> no worries
[16:55] <mup> Bug #1472338 opened: Failed to refresh power state and unhandled errors -  exceptions.OSError: [Errno 12] Cannot allocate memory <oil> <MAAS:New> <https://launchpad.net/bugs/1472338>