DNS config is invalid after a node gets enlisted.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Jeroen T. Vermeulen | ||
maas (Ubuntu) |
Fix Released
|
Critical
|
Andres Rodriguez | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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/
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 DNSForwardZoneC
== TEST CASE ==
1. Install MAAS and manage DHCP/DNS server.
2. Enlist machine
3. Make sure DNS config is correct
Tested in the lenovo lab. No CNAME records appear in the zone.master file.
Related branches
- John A Meinel (community): Approve
-
Diff: 53 lines (+25/-6)2 files modifiedsrc/provisioningserver/dns/config.py (+9/-6)
src/provisioningserver/dns/tests/test_config.py (+16/-0)
- Julian Edwards (community): Approve
-
Diff: 60 lines (+23/-3)3 files modifieddebian/changelog (+21/-1)
debian/extras/maas-region-celeryd (+1/-1)
debian/rules (+1/-1)
summary: |
- DNS config is left invalid after a node gets enlisted. + DNS config is invalid after a node gets enlisted. |
Changed in maas: | |
milestone: | none → 12.10 |
Changed in maas: | |
assignee: | nobody → Jeroen T. Vermeulen (jtv) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
tags: | added: sru-12.10 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas (Ubuntu): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
importance: | Undecided → Critical |
status: | New → In Progress |
description: | updated |
Changed in maas (Ubuntu): | |
status: | In Progress → Fix Committed |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
description: | updated |
Changed in maas (Ubuntu Precise): | |
status: | New → Fix Released |
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/ PerformingSRUVe rification . Thank you in advance!