[00:28] <spaok> anyone know how to curl against MAAS's oauth?
[01:34] <pmatulis> what do you mean?
[01:52] <spaok> pmatulis: instead of using python or ruby, using curl to make the oauth request to MAAS, kinda like this https://labs.hybris.com/2012/06/18/trying-out-oauth2-via-curl/
[01:57] <pmatulis> i don't know
[05:36] <RODOLFO> HI PLEASE  I NEED A LITTLE HELP BUT I DONT SPEAK ENGLISH ONLY A LITTLE BET
=== frankban|afk is now known as frankban
[09:41] <mup> Bug #1635493 changed: A wishlist to be able to destroy root filesystem after release <MAAS:Invalid> <https://launchpad.net/bugs/1635493>
=== mmcc_ is now known as mmcc
=== iatrou_ is now known as iatrou
=== alanmeadows_ is now known as alanmeadows
[10:47] <junaidali> thanks roaksoax
[14:42] <mup> Bug #1646133 opened: [Device discovery] Show Last seen relevant to now <ui> <MAAS:New> <https://launchpad.net/bugs/1646133>
=== deej` is now known as deej
[16:18] <mup> Bug #1646160 opened: [2.1] Device discovery UI does not have a loading state <ui> <MAAS:In Progress by ricgard> <https://launchpad.net/bugs/1646160>
[16:18] <mup> Bug #1646162 opened: [2.1] Sticky header has been removed <ui> <MAAS:In Progress by ricgard> <https://launchpad.net/bugs/1646162>
[16:18] <mup> Bug #1646163 opened: [2.1] Icon need to be improved <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1646163>
=== frankban is now known as frankban|afk
[20:51] <BloqueNegro> hi all together :(
[20:52] <BloqueNegro> i tried setting up a test environment for openstack today, however, i failed already with maas
[20:52] <BloqueNegro> set up 3 nodes on esxi, all in one net, installed maas from a server info like here: http://maas.io/docs/en/installconfig-server-iso
[20:53] <BloqueNegro> then booted my other hosts which found the maas dhcp and booted
[20:54] <BloqueNegro> however, then i tried to add the power settings (with VMWare as BMC) and just got 'No rack controllers can access the BMC of node: amused-lemur'
[20:55] <BloqueNegro> the exact same data was working with maas 1.9 on 14.04, however there we ran into ssl issues later deploying landscape. and since the destination setup will work with 16.04 we need to get maas 2 running anyway
[20:55] <BloqueNegro> anybody got an idea what is causing that kind of trouble?
[21:08] <mup> Bug #1281758 opened: re-installing maas-region-controller fails <docteam> <MAAS:Expired> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1281758>
[23:42] <gottaloveit> looking for help please.  noob to maas, but not to linux and everything else.  i can't get nodes to commission.  and things like the "backdoor" user in the image, touching a file '/tmp/block-poweroff' like the docs say to prevent the scripts from auto powering down the node, just do not work at all.  its really frustrating.  does anyone have a quick checklist of things to look for that are easily overlooked?