Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The ipa-replica-install and ipa-ca-install utilities failed when installing a replica of a Red Hat Enterprise Linux 6 master with a self-signed CA certificate. This updates fixes the bug. Note that after running ipa-ca-install, you must run the ipa-certupdate utility.
Also, it is not possible to install a replica with a CA certificate against a master that uses a third-party certificate for the httpd service. To work around this problem, issue a temporary IdM certificate for httpd on the master before installing the replica:
# certutil -d /etc/httpd/alias -L -n [NICKNAME] -r >backup.crt.der
# ipa service-mod HTTP/[HOSTNAME] --certificate=
# ipa-getcert start-tracking -d /etc/httpd/alias -n [NICKNAME]
-p /etc/httpd/alias/pwdfile.txt -C /usr/lib64/ipa/certmonger/restart_httpd
# ipa-getcert resubmit -d /etc/httpd/alias -n [NICKNAME] -K HTTP/[HOSTNAME]
After installing the replica, revert to the original certificate:
# ipa-getcert stop-tracking -d /etc/httpd/alias -n [NICKNAME]
# certutil -d /etc/httpd/alias -D -n [NICKNAME]
# certutil -d /etc/httpd/alias -A -n [NICKNAME] -t ,, -i backup.crt.der
# systemctl restart httpd
The impact is that installing a replica with a CA is not possible against a master which uses a 3rd party cert for httpd.
The workaround is to issue a (temporary) IPA cert for httpd on the master before installing the replica:
# certutil -d /etc/httpd/alias -L -n $NICKNAME -r >backup.crt.der
# ipa service-mod HTTP/$HOSTNAME --certificate=
# ipa-getcert start-tracking -d /etc/httpd/alias -n $NICKNAME -p /etc/httpd/alias/pwdfile.txt -C /usr/lib64/ipa/certmonger/restart_httpd
# ipa-getcert resubmit -d /etc/httpd/alias -n $NICKNAME -K HTTP/$HOSTNAME
After installing the replica, you can revert to the original cert:
# ipa-getcert stop-tracking -d /etc/httpd/alias -n $NICKNAME
# certutil -d /etc/httpd/alias -D -n $NICKNAME
# certutil -d /etc/httpd/alias -A -n $NICKNAME -t ,, -i backup.crt.der
# systemctl restart httpd
Verified using IPA server version ::
ipa-server-4.2.0-15.el7_2.10.x86_64
Please find the console.log for each ticket in attachments.
For https://fedorahosted.org/freeipa/ticket/5636 ticket, there is another bug reported - BZ1318616
Comment 10Abhijeet Kasurde
2016-03-17 12:26:56 UTC
The workaround for bug 1318616 is to run ipa-certupdate right after ipa-ca-install.
To make the workaround actually work, the fix for IPA ticket 5506 needs to be included as well. Moving back to POST.
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.
https://rhn.redhat.com/errata/RHBA-2016-1036.html