Bug 1476760

Summary: Overcloud deployment doesn't set the hostname in /etc/host in the deployed nodes
Product: Red Hat OpenStack Reporter: Siggy Sigwald <ssigwald>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: aschultz, dbecker, emacchi, jslagle, mburns, morazi, ohochman, rhel-osp-director-maint, tvignaud
Target Milestone: gaKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1486398 1488239 1488243 1489598 (view as bug list) Environment:
Last Closed: 2017-12-13 21:45:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1486398, 1488239, 1488243, 1489598    

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:
https://bugzilla.redhat.com/show_bug.cgi?id=1412352
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.

https://access.redhat.com/errata/RHEA-2017:3462