=== alexpilotti_ is now known as alexpilotti
[02:36] <mup> Bug #1542761 opened: MAAS will not import images and there is no error as to why <MAAS:New> <https://launchpad.net/bugs/1542761>
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
[20:28] <nagyz> haasn, RAID needs 1.9 AFAIK
[20:28] <haasn> nagyz: yeah saw that as well after upgrading to 1.9
[20:29] <nagyz> no idea about the virsh stuff but if it's a bug then go ahead and open it
[20:29] <nagyz> ah reading back I see you've found it :)
[21:59] <haasn> heh
[21:59] <haasn> maas update from 1.8 to 1.9 made the entire subnet unreachable
[22:00] <haasn> because while in the past it would default to using the external DHCP addresses when assigning web servers, it now defaults to “auto assign” which means the first vm I deployed ended up as X.X.X.1, which is the same address as my gateway
[22:00] <haasn> that was a “fun” bug to track down
[22:00] <haasn> it would be great if I could reverse this behavior without having to “upgrade” back to 1.8
[22:00] <haasn> s/when assigning web servers/when deploying nodes/
[22:08] <haasn> or even better: get the IP that was offered via DHCP during the commissioning phase, and then use that as a static IP
[22:08] <haasn> that would be the best-of-all worlds solution
[22:08] <haasn> Also, the default should be configurable rather than “auto assign”
[22:10] <haasn> Or even better: if no network range is configured for the cluster controller, the “auto assign” options shouldn't even be *available*
[22:11] <haasn> It *can't* reasonably auto-assign an address if the cluster controller is unavailable
[22:11] <haasn> I mean if the network range is unavailable