[03:44] <mup> Bug #1527068 opened: maas 1.8 static ips not released upon device removal <ci> <destroy-environment> <maas-provider> <network> <regression> <juju-core:Incomplete> <juju-core 1.25:Triaged> <MAAS:New> <https://launchpad.net/bugs/1527068>
[04:18] <mup> Bug #1511027 changed: No DNS record added for deployed machine <canonical-bootstack> <MAAS:Expired> <https://launchpad.net/bugs/1511027>
[04:27] <mup> Bug #1511027 opened: No DNS record added for deployed machine <canonical-bootstack> <MAAS:Expired> <https://launchpad.net/bugs/1511027>
[04:30] <mup> Bug #1511027 changed: No DNS record added for deployed machine <canonical-bootstack> <MAAS:Expired> <https://launchpad.net/bugs/1511027>
[10:03] <mup> Bug #1531215 changed: Failed creating DB in a fresh 1.9.0 install <MAAS:Invalid> <https://launchpad.net/bugs/1531215>
[10:33] <mup> Bug #1531456 opened: Problems syncing images are misrepresented in UI <confusing-ui> <MAAS:Triaged> <https://launchpad.net/bugs/1531456>
[12:04] <jam> blake_r: I just upgraded to 1.9 and juju is failing to bootstrap on my virtual instances
[12:04] <jam> It is saying that "there is no storage" and commissioning will detect storage
[12:05] <jam> but after clicking commissioning again, the machine starts up, and there is still no storage info.
[12:05] <jam> and the node can't be used.
[13:20] <jam> I filed bug #1531493 about this
[13:31] <mup> Bug #1531493 opened: MAAS 1.9.0 fails to detect storage for KVM instances <storage> <MAAS:New> <https://launchpad.net/bugs/1531493>
[13:34] <mup> Bug #1531493 changed: MAAS 1.9.0 fails to detect storage for KVM instances <storage> <MAAS:New> <https://launchpad.net/bugs/1531493>
[13:37] <mup> Bug #1531493 opened: MAAS 1.9.0 fails to detect storage for KVM instances <storage> <MAAS:Invalid> <https://launchpad.net/bugs/1531493>
[13:55] <mup> Bug #1531493 changed: MAAS 1.9.0 fails to detect storage for KVM instances <storage> <MAAS:Invalid> <https://launchpad.net/bugs/1531493>
[15:52] <mup> Bug #1531531 opened: 1.9 rc4: third-party driver not getting installed for storage device <oil> <MAAS:New> <https://launchpad.net/bugs/1531531>
[15:55] <mup> Bug #1531531 changed: 1.9 rc4: third-party driver not getting installed for storage device <oil> <MAAS:New> <https://launchpad.net/bugs/1531531>
[15:58] <mup> Bug #1531531 opened: 1.9 rc4: third-party driver not getting installed for storage device <oil> <MAAS:New> <https://launchpad.net/bugs/1531531>
[17:38] <roguebeard_> Hello all.  Would anyone be able to answer a question about configuring MAAS DNS?
[17:39] <roguebeard_> I have a working MAAS cluster that had DHCP enabled but not DNS.  I just enabled DNS yesterday, and I still cant resolve node names, only IPs
[17:40] <roguebeard_> Do I have to do any extra configuration to get DNS to work?  I have tried restarting the services and rebooting the MAAS controller, but still nada
[19:04] <roll4life24x7> is it possible in maas 1.9 to specify that a disk should be xfs formatted?
[19:07] <roll4life24x7> thinking specifically about ceph deployments.  is this not necessary since the juju charm will format the disks to xfs?
[19:50] <mup> Bug #1527068 changed: MAAS retains child devices' IP addresses when a parent node is released <ci> <destroy-environment> <maas-provider> <network> <regression> <juju-core:Incomplete> <juju-core 1.25:Triaged> <MAAS:Fix Released by mpontillo> <MAAS 1.8:Won't Fix> <https://launchpad.net/bugs/1527068>
[19:50] <mup> Bug #1531600 opened: Pending Power Check can interrupt Commission <MAAS:New> <https://launchpad.net/bugs/1531600>
[23:16] <dbainbri> Hello. I am new to MAAS, so a little help would, well, help. I have the MAAS server up and running and have enlisted nodes. The node PXE boot and seem to complete commissioning as they are moved to a "Ready" state. On the "nodes" list they do have a "red dot error" beside them, which is a concern. The other concern is the systems keep shutting down after i start them, MAAS seems to keep telling them to shutdown. What is the best way t
[23:51] <wililupy> Question: How do we adjust the timeout on commissioning a node? 20 minutes is not long enough for some of my servers (takes almost 10 just to boot up with 16TB of RAM)