MAAS creates DNS record against Alias when it is part of the PXE interface

Bug #1516815 reported by Andres Rodriguez on 2015-11-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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

Changed in maas:
importance: Undecided → Critical
milestone: none → 1.9.0
Mike Pontillo (mpontillo) wrote :

Can you run "sudo maas-region-admin dbshell" and pastebin the output of this query:

... then run this query and tell me the expected/actual values:

Mike Pontillo (mpontillo) wrote :

(the 2nd query, by the way, tells you the MAAS-calculated DHCP mapping as of the current release candidate.)

Mike Pontillo (mpontillo) wrote :

Looking at the 2nd query, I think I see what the issue might be.

When deciding what to put in DNS, the algorithm first prefers STICKY and USER_RESERVED IP addresses before checking the interface type.

We can change the query to first consider interface type, *then* consider IP address type, if that's the requirement. Let me know.

Mike Pontillo (mpontillo) wrote :

Finally, can you run this query and let me know if the mapping is what you expect:

Andres Rodriguez (andreserl) wrote :

Hi Mike,

This is easily reproduceable in any environment. I have reproduced it in our lab, look for the 'all-weather' machine, and you will see.


Mike Pontillo (mpontillo) wrote :

It's not an issue of how reproducible it is, it's an question of "does the query I provided output the host maps you expect" (and if not, why not?). It's a complex query, so it's best to check it against your expectations before I push another branch.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers