If a user attempts to setup a baremetal host and forgets to set the hostname via hostnamectl(see baremetal note under step 1 of http://tripleo.org/installation/installation.html), a unhandled exception is dumped straight to the user with a terse error message.
The exception should be caught and better messaging should be provided to the end user as to how to address this issue as it may not be obvious the solution in its current form.
[centos@undercloud ~]$ openstack undercloud install
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
Password:
Logging to /home/centos/.instack/install-undercloud.log
Checking for a FQDN hostname...
Static hostname detected as undercloud.localdomain
Transient hostname detected as undercloud
Static hostname "undercloud.localdomain" does not match transient hostname "undercloud".
Use hostnamectl to set matching hostnames.
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1063, in install
_validate_configuration()
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 610, in _validate_configuration
_check_hostname()
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 545, in _check_hostname
raise RuntimeError('Static and transient hostnames do not match')
RuntimeError: Static and transient hostnames do not match
Command 'instack-install-undercloud' returned non-zero exit status 1
[centos@undercloud ~]$
Fix proposed to branch: master
Review: https:/