[02:13] Bug #1522225 opened: Migration 0181 can fail on upgrade from 1.8 to 1.9 if disks across nodes have duplicate serial numbers [07:52] Bug #1522294 opened: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases === Guest32965 is now known as CyberJacob [10:18] Hi everyone, I'm currently fooling around with maas and maas seems to have trouble generating the zone configuration file for bind9. The zone is visible but the discovered/commisioned/deployed machines do not end up there, so they're not resolvable via dns. I'm running maas 1.8.3 (stable) on a clean ubuntu 15.10, this issue occurs both with vms (bridged) and physical machines (5nics) [10:19] The log tells me, that it is updating the mentioned zone file when a new node is discovered, but the zone file stays "empty", ie there are no entries for the nodes in there [14:02] cmagina: only deployed nodes will end up with a DNS zone [14:02] errr [14:02] cmagina: sorry [14:02] CruX__: [14:02] CruX__: ^^ [14:03] CruX__: nodes that are being commissioned will end up with DNS based on IP [14:06] roaksoax: np [14:57] Bug #1522294 changed: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [15:00] Bug #1522294 opened: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [15:09] Bug #1522294 changed: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [15:45] roaksoax: okay, I guess I'll try again then. Thanks [17:42] Bug #1522294 opened: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [17:51] Bug #1522294 changed: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [18:00] Bug #1522294 opened: MAAS dhcp fails to parse leases written to /var/lib/maas/dhcpd.leases [18:00] Bug #1522512 opened: Nodes in Ready state transitioning to Commissioning which are already powered on should be rebooted automatically