overcloud deployment fails with `Unable to resolve all hostnames` in Red Hat OpenStack Platform
Issue
Overcloud deployment fails with Unable to resolve all hostnames in Red Hat OpenStack Platform.
The error message states that hostnames cannot be resolved:
(...) Error: Unable to communicate with overcloud-controller-1\u001b[0m\n\u001b[mNot[29/1992]
ge[main]/Pacemaker::Corosync/Exec[reauthenticate-across-all-nodes]/returns: Error: Unable to communicate with overcloud-controller-
0\u001b[0m\n\u001b[mNotice: /Stage[main]/Pacemaker::Corosync/Exec[Create Cluster tripleo_cluster]/returns: Error: Unable to resolve all hostnames, use --force to override (...)
/etc/hosts on the controllers is not populated with all hostname entries, only the VIPs appear:
# HEADER: This file was autogenerated at 2017-04-17 09:01:30 -0400
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
192.168.5.108 overcloud.storagemgmt.localdomain # FQDN of the storage mgmt VIP
192.168.1.14 overcloud.ctlplane.localdomain # FQDN of the ctlplane VIP
192.168.4.108 overcloud.internalapi.localdomain # FQDN of the internal api VIP
192.168.2.101 overcloud.storage.localdomain # FQDN of the storage VIP
192.168.114.105 overcloud.localdomain # FQDN of the external VIP
Environment
Red Hat OpenStack Platform 10
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
