MAAS creates DNS record against Alias when it is part of the PXE interface
Bug #1516815 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned | ||
1.9 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
And alias got created against the MAAS PXE interface (eth0), and it got configured to receive an IP address via 'Auto Assign'.
However, on deploy, the DNS record got created against the alias (eth0:1) instead of the actual physical interface.
Related branches
lp:~mpontillo/maas/fix-1516815
- Andres Rodriguez (community): Approve
-
Diff: 75 lines (+35/-12)2 files modifiedsrc/maasserver/models/staticipaddress.py (+12/-12)
src/maasserver/models/tests/test_staticipaddress.py (+23/-0)
lp:~mpontillo/maas/fix-1516815-1.9
- Mike Pontillo (community): Approve
-
Diff: 75 lines (+35/-12)2 files modifiedsrc/maasserver/models/staticipaddress.py (+12/-12)
src/maasserver/models/tests/test_staticipaddress.py (+23/-0)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 1.9.0 |
To post a comment you must log in.
Can you run "sudo maas-region-admin dbshell" and pastebin the output of this query:
http:// paste.ubuntu. com/13303708/
... then run this query and tell me the expected/actual values:
http:// paste.ubuntu. com/13251194/