Validating domain name in FQDN and openstack_domain variable

Bug #1670874 reported by Vitaliy Nogin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Won't Fix
Low
Unassigned

Bug Description

In inventory/group_vars/all.yml file and in openstack_hosts/defaults/main.yml role openstack_domain variable defined as openstack.local

openstack_domain: openstack.local

However, during OSA deployment by some reason, we use FQDN name.

In /etc/hosts file all hosts populated with openstack.local domain name:

root@728987-comp-disk-238:/etc/ansible# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 728987-comp-disk-238.local.lan 728987-comp-disk-238

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.20.112.63 729359-comp-disk-335.openstack.local 729359-comp-disk-335
172.20.112.51 729075-comp-disk-290.openstack.local 729075-comp-disk-290
---------------- skipped by vnogin ----------------------------------
172.20.114.149 729018-comp-disk-254-heat-engine-container-560ada15.openstack.local 729018-comp-disk-254-heat-engine-container-560ada15 729018-comp-disk-254_heat_engine_container-560ada15
172.20.112.155 728987-comp-disk-238-rsyslog-container-2fba7186.openstack.local 728987-comp-disk-238-rsyslog-container-2fba7186 728987-comp-disk-238_rsyslog_container-2fba7186
172.20.112.55 728987-comp-disk-238.openstack.local 728987-comp-disk-238

Nevertheless, nova uses FQDN domain:

root@729013-comp-disk-259-utility-container-c71251fe:~# nova hypervisor-list
+-----+--------------------------------+-------+---------+
| ID | Hypervisor hostname | State | Status |
+-----+--------------------------------+-------+---------+
| 2 | 729075-comp-disk-290.local.lan | up | enabled |
| 5 | 729359-comp-disk-335.local.lan | up | enabled |
---------------- skipped by vnogin ---------------------
| 155 | 729675-comp-disk-217.local.lan | up | enabled |
| 158 | 729002-comp-disk-223.local.lan | up | enabled |
+-----+--------------------------------+-------+---------+

After deployment, we don't have compute nodes with proper functionality and due to this fact we not able to perform live migration (for instance).

From my point of view, we need to have validation for a domain name in FQDN and openstack_domain variable for avoiding such problems after deployment.

Regards,
Vitaliy

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Please see our triage conversation:

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Jonathan Rosser (jrosser) wrote :

Closing this bug due to age, and openstack-ansible not being opionated about how operators setup their hosts/domains in DNS or otherwise.

Changed in openstack-ansible:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.