dhcp agent configured with mismatching domain and host entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Queens |
Fix Released
|
Undecided
|
Unassigned | ||
Rocky |
Fix Released
|
Undecided
|
Unassigned | ||
Stein |
Fix Released
|
Undecided
|
Unassigned | ||
Train |
Fix Released
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
Undecided
|
James Page | ||
neutron (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Unassigned | ||
Cosmic |
Fix Released
|
High
|
Unassigned | ||
Disco |
Fix Released
|
High
|
Unassigned | ||
Eoan |
Fix Released
|
High
|
Unassigned |
Bug Description
Related bug 1774710 and bug 1580588
The neutron-dhcp-agent in OpenStack >= Queens makes use of the dns_domain value set on a network to configure the '--domain' parameter of the dnsmasq instance that supports it; at the same time, neutron makes use of CONF.dns_domain when creating dns_assignments for ports - this results in a hosts file for the dnsmasq instance which uses CONF.dns_domain and a --domain parameter of network.dns_domain which do not match.
This results in a search path on instances booted attached to the network which is inconsistent with the internal DNS entries that dnsmasq responds with:
root@
222.21.
root@
bionic-
In the above example:
CONF.dns_domain = jamespage.internal.
network.
Based on previous discussion in bug 1580588 I think that the dns_domain value for a network was intented for use for external DNS integration such as that provided by Designate.
The changed made under commit:
https:/
appear to break this assumption, producing somewhat inconsistent behaviour in the dnsmasq instance for the network.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → Miguel Lavalle (minsel) |
Changed in neutron: | |
assignee: | James Page (james-page) → Miguel Lavalle (minsel) |
Changed in neutron (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in neutron (Ubuntu Cosmic): | |
status: | New → Triaged |
Changed in neutron (Ubuntu Disco): | |
status: | New → Triaged |
Changed in neutron (Ubuntu Eoan): | |
status: | New → Triaged |
Changed in neutron (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in neutron (Ubuntu Cosmic): | |
importance: | Undecided → High |
Changed in neutron (Ubuntu Disco): | |
importance: | Undecided → High |
Changed in neutron (Ubuntu Eoan): | |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | added: neutron-easy-proactive-backport-potential |
Is this simple enough to reproduce with devstack?
If so can you please share the steps to do so?
Thanks