MaaS DNS - named, not loaded due to errors.

[Thiago Martins]

Hi!

 I think I found one bug with MaaS DNS subsystem. Brand new MaaS using Ubuntu 12.10.

 My first two nodes of my MaaS was added into the system via DHCP + PXE, not by clicking on "+Add node" button.

/var/log/syslog:
Oct 21 17:55:58 seed1 named[959]: dns_master_load: /etc/bind/maas/zone.teste.com:4112: 192-168-50-1.teste.com: CNAME and other data
Oct 21 17:55:58 seed1 named[959]: zone teste.com/IN: loading from master file /etc/bind/maas/zone.teste.com failed: CNAME and other data
Oct 21 17:55:58 seed1 named[959]: zone teste.com/IN: not loaded due to errors.

Bind9 does not start anymore.

The contents of line 4112 of file /etc/bind/maas/zone.teste.com:

---
192-168-50-1 IN CNAME 192-168-50-1
---

The output of "grep 192-168-50-1\ /etc/bind/maas/zone.teste.com":
192-168-50-1 IN A 192.168.50.1
192-168-50-1 IN CNAME 192-168-50-1

 It is intended to have two "192-168-50-1" entries there?!

 BTW, 192-168-50-1 (and 192-168-50-2) was my first (and second) node started first via DHCP / PXE...

Line of second node (zone.teste.com):
192-168-50-2 IN CNAME 192-168-50-2

 When I commend the line 4112, bind stops at next line, of my second node... When I commend out those two, bind9 start up again.

 I think MaaS DNS subsystem isn't ready for production. I'll try MaaS only with DHCP managed and with only 1 ethernet on its machine.

 Also, my third node was added by clicking on "+Add node" and I don't know if this DNS problem appear after or before that.

Tks!
Thiago

[Raphaël Badin (rvb)]

This is a duplicate of bug 1066958 which is fixed in the current trunk. This will be part of the upcoming SRU package.