[04:07] <mup> Bug #1496360 opened: POST request using python-maas-client <MAAS:Incomplete> <https://launchpad.net/bugs/1496360>
[04:51] <binoy> https://bugs.launchpad.net/maas/+bug/1496360
[07:32] <binoy> hi
[07:32] <binoy> https://bugs.launchpad.net/maas/+bug/1496360
[07:36] <binoy> how to implement post with data in maas api
[12:45] <kiko> good morning
[16:56] <mup> Bug #1496360 changed: POST request using python-maas-client <MAAS:Invalid> <https://launchpad.net/bugs/1496360>
[18:36] <mup> Bug #1496961 opened: Ephemeral environment during curtin installation doesn't use proxy <MAAS:Confirmed> <https://launchpad.net/bugs/1496961>
[19:09] <mup> Bug #1402042 changed: console= parameters need to be added before -- on kernel cmdline <verification-done> <curtin:Fix Committed> <MAAS:Fix Committed> <MAAS 1.7:Triaged> <MAAS 1.8:Fix Released> <MAAS trunk:Fix Committed> <curtin (Ubuntu):Fix Released> <debian-installer (Ubuntu):Fix Released>
[19:09] <mup> <debian-installer-utils (Ubuntu):Fix Released> <maas (Ubuntu):Fix Released> <debian-installer-utils (Ubuntu Precise):Fix Released by mathieu-tl> <maas (Ubuntu Precise):Confirmed> <curtin (Ubuntu Trusty):Confirmed> <debian-installer (Ubuntu Trusty):Fix Released> <debian-installer-utils (Ubuntu
[19:09] <mup> Trusty):Fix Released by mathieu-tl> <maas (Ubuntu Trusty):Confirmed> <curtin (Ubuntu Utopic):Won't Fix> <debian-installer (Ubuntu Utopic):Fix Released> <debian-installer-utils (Ubuntu Utopic):Fix Released by mathieu-tl> <maas (Ubuntu Utopic):Confirmed> <curtin (Ubuntu Vivid):Confirmed>
[19:09] <mup> <debian-installer (Ubuntu Vivid):Fix Released> <debian-installer-utils (Ubuntu Vivid):Fix Released> <maas (Ubuntu Vivid):Confirmed> <curtin (Ubuntu Wily):Fix Released> <debian-installer (Ubuntu Wily):Fix Released> <debian-installer-utils (Ubuntu Wily):Fix Released> <maas (Ubuntu Wily):Fix Released>
[19:09] <mup> <Debian:Fix Released> <https://launchpad.net/bugs/1402042>
[21:50] <catbus1> blake_r: Hi, about the sles deploy, the installation output says it's finished, but MAAS reports failed deployment. I have seen this before, but the next time I deployed when it happened before, it worked.
[21:50] <catbus1> blake_r: now I have re-deployed sles several times with consistent failed deployment result.
[21:51] <catbus1> blake_r: what does MAAS do in the final stage when the node installation is finished?
[21:54] <blake_r> catbus1: it needs to reboot and cloud-init talk to maas which looks like its not working
[21:55] <catbus1> I have seen it working before. I am recommissioning the server to double check. We had several changes on the network interface configuration recently. But I remember we had recommissioned all server earlier after the last maas network change.
[21:56] <catbus1> s/server/servers
[22:50] <catbus1> blake_r: still the same.
[22:50] <catbus1> blake_r: there wasn't much traffic on that network. the only other area where I think is a problem is we used to use 10G to provision bare metal, now we are using 1G.
[22:51] <catbus1> we have no problem provisioning ubuntu server with maas, all the time.
[23:40] <dannf> is there something that needs to be done to "activate" maas-dhcp other than installing it? my /etc/maas/dhcpd.conf just says "# DHCP server stopped and disabled."