[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Changed in: maas (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Also affects: maas (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Tags removed: verification-needed ** Tags added: verification-done ** Description changed: After a node gets enlisted, its hostname is set to a generated address based on its IP address (e.g. 192-168-10-10). When the DNS config gets written, if the hostname is not changed to a custom value, the CNAME record conflicts with a pre-populated A record for that IP: Content of /etc/bind/maas/zone.master IN NS master. master. IN A 192.168.10.1 [...] 192-168-10-10 IN A 192.168.10.10 [...] 192-168-10-10 IN CNAME 192-168-10-10 One solution is to change DNSForwardZoneConfig.get_cname_mapping so that the records where generated_hostname(ip) == hostname are filtered out. == TEST CASE == 1. Install MAAS and manage DHCP/DNS server. - 2. Enlist machine + 2. Enlist machine 3. Make sure DNS config is correct + + Tested in the lenovo lab. No CNAME records appear in the zone.master + file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
This bug was fixed in the package maas - 0.1+bzr1269+dfsg-0ubuntu1 --- maas (0.1+bzr1269+dfsg-0ubuntu1) quantal-proposed; urgency=low * New upstream bugfix release - Fixes commissioning failing to set memory attribute. (LP: #1064638) - Fixes node listing by adding pagination (LP: #1064672) - Changes default bind rndc key which breaks initscripts (LP: #1066938) - Fixes invalid DNS config once node is enlisted (LP: #1066958) - Reference documentation link to correct URL (LP: #1067261) [ Andres Rodriguez ] * debian/rules: Change upstream branch. [ Gavin Panella ] * debian/maas-dns.postinst: Remove MAAS-related include lines from named's config before adding a new one (LP: #1066929) [ Raphael Badin ] * debian/extras/maas-region-celeryd: Remove whitespace that affects DNS rabbitmq queue. (LP: #1067929) -- Andres RodriguezTue, 16 Oct 2012 10:31:37 -0400 ** Changed in: maas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Description changed: After a node gets enlisted, its hostname is set to a generated address based on its IP address (e.g. 192-168-10-10). When the DNS config gets written, if the hostname is not changed to a custom value, the CNAME record conflicts with a pre-populated A record for that IP: Content of /etc/bind/maas/zone.master IN NS master. master. IN A 192.168.10.1 [...] 192-168-10-10 IN A 192.168.10.10 [...] 192-168-10-10 IN CNAME 192-168-10-10 One solution is to change DNSForwardZoneConfig.get_cname_mapping so that the records where generated_hostname(ip) == hostname are filtered out. - == TEST == - This fix has been tested on both canonistack and in the lenovo lab. + == TEST CASE == + 1. Install MAAS and manage DHCP/DNS server. + 2. Enlist machine + 3. Make sure DNS config is correct -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
Hello Raphaël, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Changed in: maas (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Description changed: After a node gets enlisted, its hostname is set to a generated address based on its IP address (e.g. 192-168-10-10). When the DNS config gets written, if the hostname is not changed to a custom value, the CNAME record conflicts with a pre-populated A record for that IP: Content of /etc/bind/maas/zone.master - IN NS master. + IN NS master. master. IN A 192.168.10.1 [...] 192-168-10-10 IN A 192.168.10.10 [...] 192-168-10-10 IN CNAME 192-168-10-10 One solution is to change DNSForwardZoneConfig.get_cname_mapping so that the records where generated_hostname(ip) == hostname are filtered out. + + == TEST == + This fix has been tested on both canonistack and in the lenovo lab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Branch linked: lp:~andreserl/maas/packaging_bzr1269_quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Changed in: maas (Ubuntu) Assignee: (unassigned) => Andres Rodriguez (andreserl) ** Changed in: maas (Ubuntu) Importance: Undecided => Critical ** Changed in: maas (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066958] Re: DNS config is invalid after a node gets enlisted.
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066958 Title: DNS config is invalid after a node gets enlisted. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs