Bug 1476760 - Overcloud deployment doesn't set the hostname in /etc/host in the deployed nodes
Summary: Overcloud deployment doesn't set the hostname in /etc/host in the deployed nodes
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
Target Milestone: ga
: 12.0 (Pike)
Assignee: Emilien Macchi
QA Contact: Gurenko Alex
Depends On:
Blocks: 1486398 1488239 1488243 1489598
TreeView+ depends on / blocked
Reported: 2017-07-31 11:55 UTC by Siggy Sigwald
Modified: 2021-03-11 15:30 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1486398 1488239 1488243 1489598 (view as bug list)
Last Closed: 2017-12-13 21:45:43 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1711435 0 None None None 2017-08-17 18:31:03 UTC
OpenStack gerrit 494669 0 None None None 2017-08-17 18:31:22 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Siggy Sigwald 2017-07-31 11:55:34 UTC
Description of problem:
The result of executing  the command  "hostname -f" in a deployed overcloud node returns "localhost" and because of that the first node registers as "localhost" in the satellite, the subsecuential node registration fails because "localhost" already exists in the satellite. 
There's a bug open for a similar problem against Mitaka (https://bugzilla.redhat.com/show_bug.cgi?id=1474092).

Comment 4 James Slagle 2017-08-17 18:32:36 UTC
this would likely need to be backported to several releases if the issue is as widespread to affect anywhere satellite 6.2.5+ is used.

there is already a bug we can use for the OSP10 backport:

Comment 9 Gurenko Alex 2017-12-13 09:10:20 UTC
Verified on build 2017-12.06.2

Comment 12 errata-xmlrpc 2017-12-13 21:45:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.