RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 990130 - Incorrect information in "ipa help host"
Summary: Incorrect information in "ipa help host"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-30 12:53 UTC by Dmitri Pal
Modified: 2014-06-18 00:10 UTC (History)
2 users (show)

Fixed In Version: ipa-3.3.0-0.2.beta2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 13:02:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dmitri Pal 2013-07-30 12:53:58 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3820

From ```ipa help host```:
{{{
A host can only be enrolled once. If a client has enrolled and needs to
be re-enrolled, the host entry must be removed and re-created. Note that
re-creating the host entry will result in all services for the host being
removed, and all SSL certificates associated with those services being
revoked.
}}}

This information is outdate. The [http://www.freeipa.org/page/V3/Forced_client_re-enrollment forced client re-enrollment] feature enables exactly that - a client can be re-enrolled without removing the host entry. The above paragraph needs to be updated with correct information with regard to client re-enrollment.

Comment 1 Martin Kosek 2013-08-06 10:32:25 UTC
Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/3bb6d3830868a50066569b55158fbba1f36654fd

Comment 3 Scott Poore 2014-01-28 17:37:24 UTC
Verified.

Version ::
ipa-server-3.3.3-15.el7.x86_64

Test Results ::

[root@master ~]# PAGER="cat" man ipa-client-install 2>/dev/null|grep "Re-enrollment of the host"
   Re-enrollment of the host

[root@master ~]# ipa help host|grep "A host can only be enrolled once"
[root@master ~]# 

From Man page:

   Re-enrollment of the host
       Requirements:

       1. Host has not been un-enrolled (the ipa-client-install --uninstall  command  has  not  been
       run).
       2. The host entry has not been disabled via the ipa host-disable command.

       If this has been the case, host can be re-enrolled using the usual methods.

       There are two method of authenticating a re-enrollment:

       1.  You  can  use --force-join option with ipa-client-install command. This authenticates the
       re-enrollment using the admin's credetials provided via the -w/--password option.
       2. If providing the admin's password via the command line is not an option (e.g you  want  to
       create a script to re-enroll a host and keep the admin's password secure), you can use backed
       up keytab from the previous enrollment of this host to authenticate. See --keytab option.

       Consenquences of the re-enrollment on the host entry:

       1. A new host certificate is issued
       2. The old host certificate is revoked
       3. New SSH keys are generated
       4. ipaUniqueID is preserved

Comment 4 Ludek Smid 2014-06-13 13:02:32 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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