Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1033204 - [RFE] Provide guidance on name resolution for foreman
[RFE] Provide guidance on name resolution for foreman
Status: CLOSED CURRENTRELEASE
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide (Show other bugs)
4.0
Unspecified Unspecified
high Severity medium
: z1
: 4.0
Assigned To: Martin Lopes
ecs-bugs
: Documentation, FutureFeature
Depends On:
Blocks: RHOS-Foreman-Deployability 1049118
  Show dependency treegraph
 
Reported: 2013-11-21 12:16 EST by james labocki
Modified: 2015-02-15 18:41 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-02-15 18:41:53 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description james labocki 2013-11-21 12:16:44 EST
Please provide guidance in the documentation on name resolution requirements for foreman

    Need to include guidance on requirements for name resolution
    [root@foreman bin]# sh foreman_server.sh 
    #################### RED HAT OPENSTACK #####################
    Thank you for using the Red Hat OpenStack Foreman Installer!
    Please note that this tool is a Technology Preview
    For more information about Red hat Technology Previews, see
    https://access.redhat.com/support/offerings/techpreview/
    ############################################################
    Press [Enter] to continue
    hostname: Unknown host
    PUPPETMASTER has a value of  but it must be a fqdn
Comment 2 Liz 2013-11-21 15:01:21 EST
I think it would be great to be consistent with how RDO has done this in their documentation:
http://openstack.redhat.com/Virtualized_Foreman_Dev_Setup#Hostname_and_FQDN
Comment 3 Martin Lopes 2014-01-09 23:18:12 EST
Ready for QA when package is available.

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