Bug 768257 - Man Page : Document client IP addressing / FQDN requirements
Man Page : Document client IP addressing / FQDN requirements
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Rob Crittenden
: ManPageChange
Depends On:
  Show dependency treegraph
Reported: 2011-12-16 02:41 EST by Martin Kosek
Modified: 2012-06-20 09:28 EDT (History)
5 users (show)

See Also:
Fixed In Version: ipa-2.2.0-11.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 09:28:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Kosek 2011-12-16 02:41:38 EST
This bug is created as a clone of upstream ticket:

Currently ipa-client-install man page states about IP addressing / hostname only that:

             The  hostname  of this server (FQDN). If specified, the hostname
             will be set and the system configuration will be updated to per-
             sist  over reboot. By default a nodename result from uname(2) is

But if one runs ipa-client-install without --hostname on a client-to-be using using dynamic IP / hostname from corporate DHCP/DNS without MAC binding then eventually the client's IP address and hostname will change causing issues on the client, e.g., with Kerberos.

Manual page should clearly state that a static hostname for clients is needed.
Comment 1 Martin Kosek 2012-02-27 11:52:41 EST
Fixed upstream. Man pages now contain a special section about hostname requirements.

master: https://fedorahosted.org/freeipa/changeset/dc47f77dc1f7df8aafa09ed6d9baa7f209016f35
ipa-2-2: https://fedorahosted.org/freeipa/changeset/cac915e607d0e4bdaf4bede36e34beb61be10d15
Comment 3 Kaleem 2012-04-19 07:39:44 EDT
Following text has been added in man page of ipa-client-install for hostname
       Client  must use a static hostname. If the machine hostname changes for example due to a dynamic hostname assignment by a DHCP server,
       client enrollment to IPA server breaks and user then would not be able to perform Kerberos authentication.

       --hostname option may be used to specify a static hostname that is set in machine system configuration and persist over reboot.

In man page of ipa-client-install, hostname switch description is changed but in ipa-client-install's help text it is still the same.

hostname switch description from ipa-client-install's help text

                        The hostname of this server (FQDN). If specified, the
                        hostname will be set and the system configuration will
                        be updated to persist over reboot. By default a
                        nodename result from uname(2) is used.

Here is above description word "server" should be changed with "machine" which has been done in man page.
Comment 4 Jenny Galipeau 2012-04-19 10:22:48 EDT
based on comments, setting bug status to Assigned
Comment 8 Martin Kosek 2012-04-19 15:29:38 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    New Contents:
No documentation needed.
Comment 9 Kaleem 2012-04-24 09:00:28 EDT

Now, ipa-client-install's help text also contains "machine" instead of "server" .

[root@dhcp201-121 ~]# rpm -q ipa-server ipa-client
[root@dhcp201-121 ~]#
Comment 11 errata-xmlrpc 2012-06-20 09:28:24 EDT
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.