Bug 1463121 - We should be more clear about the hostname setting for the IPA container
We should be more clear about the hostname setting for the IPA container
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Using-Containerized-Identity-Management-Services (Show other bugs)
7.4
All Linux
high Severity medium
: rc
: ---
Assigned To: Aneta Šteflová Petrová
ipa-qe
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-20 03:52 EDT by Thorsten Scherf
Modified: 2017-06-20 04:07 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Thorsten Scherf 2017-06-20 03:52:11 EDT
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7.4-beta/html/using_containerized_identity_management_services/deploying-an-identity-management-server-in-a-container#deploying-server-prerequisites-and-recommendations-deploying-an-identity-management-server-in-a-container

Section Number and Name: 
2.3. Installing an Identity Management Server in a Container: Basic Installation

Describe the issue: 

In the doc we say:

"""
Use the atomic install rhel7/ipa-server --hostname fully_qualified_domain_name command to start the installation. 
""" 

And also:

"""
To prevent the installation from failing, always use the --hostname option with atomic install to set the fully-qualified host name (FQDN) of the new Identity Management system. 
"""

We should be more clear here that the IPA container requires its own hostname which is also resolvable via DNS and/or /etc/hosts. The IPA container is network namespaced (SSSD container is not) and will therefore also get its own IP address.

If people just do something like "--hostname `hostname` during the container setup, the IPA container will use the same hostname which is also used on the Atomic host. When you now try to enroll a SSSD container into the new IPA domain, the enrollment will fail because the ipa-client-install script tried to connect to the Atomic host rather than the IPA container.



Suggestions for improvement: 

Additional information:

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