[01:16] <fluxcore> Hi fellows. Just trying to install my first bootstack cluster using maas/juju - and all my nodes timeout (20mins) during commissioning. I've tried sshing into the node and poking around log files but can't see any smoking guns - how do I go about debugging what the issue is?
[02:51] <fluxcore> bah, wiping install and trying with 15.10 instead.
=== narindergupta is now known as narindergupta_aw
=== bradm_ is now known as bradm
[06:46] <mup> Bug #1540765 opened: [1.10] Unable to detect IPMI control settings during enlistment <MAAS:New> <https://launchpad.net/bugs/1540765>
[06:46] <mup> Bug #1540766 opened: [1.10] VLAN submission to MAAS during enlistment leaks Python-isms <MAAS:New> <https://launchpad.net/bugs/1540766>
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
=== cpaelzer is now known as cpaelzer_afk
=== plars_ is now known as plars
=== cpaelzer_afk is now known as cpaelzer
[13:45] <icey_> I'm running MAAS on an orangebox with Juju, it looks like cloud-init on these is dropping the upstream DNS into the resolvconf
[13:48] <icey_> is there something I should be doing differently or some config option that I'm missing?
[13:49] <icey_> the additional DNS entry matches the default gateway but doesn't let me resolve the other MAAS nodes within the cluster
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
[17:29] <mup> Bug #1541030 opened: commission fails with HTTP Error 400: BAD REQUEST <MAAS:New> <https://launchpad.net/bugs/1541030>
[17:32] <mup> Bug #1541030 changed: commission fails with HTTP Error 400: BAD REQUEST <MAAS:New> <https://launchpad.net/bugs/1541030>
[17:38] <mup> Bug #1541030 opened: commission fails with HTTP Error 400: BAD REQUEST <MAAS:New> <https://launchpad.net/bugs/1541030>
=== cpaelzer_ is now known as cpaelzer_afk
[18:29] <fluxcore> How do I get MAAS to allow other commissioning images than 14.04LTS? I've installed the 15.10 boot image, but it only shows up in the deployment dropdown, not commissioning.
[18:31] <fluxcore> my nodes all fail to commission due to SSL cert issues, and there's a but which claims to fix it in later versions of pollinate
[18:31] <fluxcore> *bug
[18:51] <nagyz> roaksoax-brb, am I supposed to be able to select multiple disks on the UI to add them to bcache?
[18:51] <nagyz> (as backing disks)
=== nagyz_ is now known as nagyz
[20:26] <Sidrick> hi there, can I use MAAS without a BMC port ?
[20:33] <mup> Bug #1541091 opened: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:New> <https://launchpad.net/bugs/1541091>
[20:33] <fluxcore> supposedly supports wake on lan...
[21:48] <mup> Bug #1541091 changed: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:Invalid> <https://launchpad.net/bugs/1541091>
[21:51] <mup> Bug #1541091 opened: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:Invalid> <https://launchpad.net/bugs/1541091>
[21:54] <fluxcore> bloody hell, is there even a way to add more commissioning images? 14.04 is broken but I can't find anything else
[22:00] <mup> Bug #1541091 changed: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:Invalid> <https://launchpad.net/bugs/1541091>
[22:03] <mup> Bug #1541091 opened: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:Invalid> <https://launchpad.net/bugs/1541091>
=== dannf` is now known as dannf
[22:06] <mup> Bug #1541091 changed: [1.9] cannot add multiple drives as bcache backing drives on the UI <MAAS:Invalid> <https://launchpad.net/bugs/1541091>
=== mthaddon` is now known as mthaddon
=== cpaelzer_afk is now known as cpaelzer_