Bug 1254370 - [Docs] [Director] Error in product documentation for setting OSP Director hostname
Summary: [Docs] [Director] Error in product documentation for setting OSP Director hos...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: Director
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 7.0 (Kilo)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 21:45 UTC by Brett Thurber
Modified: 2016-01-11 10:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-11 10:12:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brett Thurber 2015-08-17 21:45:45 UTC
Description of problem:
When executing openstack undercloud install, it fails with: Error: curl -k --noproxy localhost --retry 30 --retry-delay 6 -f -L -o /var/lib/rabbitmq/rabbitmqadmin http://guest:guest@localhost:15672/cli/rabbitmqadmin returned 7 instead of one of [0]

Version-Release number of selected component (if applicable):
OSPd

How reproducible:
Every time

Steps to Reproduce:
1.  Following the product docs, configuring the hostname for the OSPd node, it mentions to edit /etc/hosts and add the following:  
"The director also requires an entry for the system’s hostname and base name in /etc/hosts. For example, if the system is named manager.example.com, /etc/hosts requires an entry like:
127.0.0.1   manager.example.com manager
2.  If following explicitly and removal of the following for the local host IP entry is done:  localhost localhost.localdomain localhost4 localhost4.localdomain4, the mentioned error occurs.


Actual results:
Error during undercloud install.

Expected results:
Explicit directions that advise not to remove the following:  localhost localhost.localdomain localhost4 localhost4.localdomain4 from 127.0.0.1 from /etc/hosts.

This allows the installation to proceed.

Additional info:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Setting_the_Hostname_for_the_System.html

Comment 3 Andrew Dahms 2015-08-21 01:54:47 UTC
Assigning to Dan for review.

Comment 4 rlopez 2015-08-24 17:06:58 UTC
To add to this hostname experience,

If you enter the following within your /etc/host

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 manager.example.com manager

If you do the above and append the hostname at the *end*, 

the following commands show:

$ hostname
manager.example.com

$ hostname -f 
localhost


^ This is a problem. To ensure you do not have this issue make sure to add manager.example.com and manager *before* localhost

i.e.

127.0.0.1   manager.example.com manager localhost localhost.localdomain localhost4 localhost4.localdomain4

Comment 6 Dan Macpherson 2015-09-09 01:43:36 UTC
This fix is now live:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Setting_the_Hostname_for_the_System.html

The examples now reads:

127.0.0.1   manager.example.com manager localhost localhost.localdomain localhost4 localhost4.localdomain4

Brett, how does this suit the requirements of this bug? Any further changes required?

Comment 7 Brett Thurber 2015-09-09 02:11:57 UTC
(In reply to Dan Macpherson from comment #6)
> This fix is now live:
> 
> https://access.redhat.com/documentation/en-US/
> Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/
> Director_Installation_and_Usage/sect-Setting_the_Hostname_for_the_System.html
> 
> The examples now reads:
> 
> 127.0.0.1   manager.example.com manager localhost localhost.localdomain
> localhost4 localhost4.localdomain4
> 
> Brett, how does this suit the requirements of this bug? Any further changes
> required?

Looks good.  Thanks!

Comment 8 Dan Macpherson 2015-09-09 03:06:21 UTC
Cool. Thanks, Brett!

Comment 9 Andrew Dahms 2016-01-11 10:12:01 UTC
This content is live on the Customer Portal.

Closing.


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