neutron-based instances should not use the nova-network 'dhcp_domain' option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Stephen Finucane |
Bug Description
There seems to be an issue with how domains get assigned when booting instances. My understanding is that with neutron, the neutron dns_domain option should be what determines the resulting domain name of the instances. However, when creating instances with the following configuration:
(undercloud) [centos@
#dns_domain = openstacklocal
dns_domain=
(undercloud) [centos@
#dhcp_domain=
dhcp_domain=
I get the following in the instance:
[heat-admin@
Static hostname: overcloud-
It looks like this is being done by cloud-init:
Jun 14 21:07:34 host-9-1-1-12 cloud-init[1405]: [CLOUDINIT] cc_set_
Jun 14 21:07:34 host-9-1-1-12 cloud-init[1405]: [CLOUDINIT] util.py[DEBUG]: Running command ['hostnamectl', 'set-hostname', 'overcloud-
So cloud-init is likely getting the host and domain name from Nova metadata, even though Neutron is being used to manage networking.
If I also set dhcp_domain as follows:
(undercloud) [centos@
#dhcp_domain=
dhcp_domain=
Then I get the expected results:
[heat-admin@
Static hostname: overcloud-
These are obviously tripleo overcloud instances being deployed via Ironic. I'm using some recent RDO packages:
$ sudo rpm -qa | grep nova
openstack-
python-
puppet-
openstack-
python2-
openstack-
openstack-
openstack-
openstack-
99bd334 is the short sha of the commit the packages were built against
$ sudo rpm -qa | grep neutron
python-
openstack-
python2-
openstack-
openstack-
puppet-
python-
openstack-
This is not ideal in any case, but it's particularly concerning since according to the opt docs dhcp_domain is deprecated.
Changed in nova: | |
assignee: | nobody → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
summary: |
- dhcp-domain is deprecated, but required for correct FQDN behavior + neutron-based instances should not use the nova-network 'dhcp_domain' + option |
Changed in nova: | |
assignee: | Stephen Finucane (stephenfinucane) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Stephen Finucane (stephenfinucane) |
There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.