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 1339304 - CA installed on replica is always marked as renewal master
Summary: CA installed on replica is always marked as renewal master
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
URL:
Whiteboard:
Depends On: 1339233
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-24 15:54 UTC by Marcel Kolaja
Modified: 2016-06-23 16:32 UTC (History)
8 users (show)

Fixed In Version: ipa-4.2.0-15.el7_2.17
Doc Type: Bug Fix
Doc Text:
When installing a clone certificate authority (CA) on a replica, the LDAP entry representing the replica was marked with the "caRenewalMaster" flag, even though another server already served as the CA renewal master. However, Identity Management (IdM) supports only one CA renewal master. Consequently, generating a new CA subsystem certificate could potentially cause the certificate to be generated multiple times, and CA operations, such as certificate renewal, could stop working on some servers. Now, the replica is no longer marked as "caRenewalMaster" in the described situation. Also, IdM removes any surplus "caRenewalMaster" flags to ensure only one CA renewal master is available. As a result, generating a CA subsystem certificate does not cause the CA operations to fail.
Clone Of: 1339233
Environment:
Last Closed: 2016-06-23 16:32:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Bug Verification console output (1.99 KB, text/plain)
2016-06-01 09:46 UTC, Nikhil Dehadrai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1256 0 normal SHIPPED_LIVE ipa bug fix update 2016-06-23 20:15:52 UTC

Description Marcel Kolaja 2016-05-24 15:54:44 UTC 
This bug has been copied from bug #1339233 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 5 Kaleem 2016-05-25 07:39:18 UTC 
Please provide the steps to verify this.
Comment 6 Jan Cholasta 2016-05-25 07:49:52 UTC 
1. install IPA server
2. install one or more IPA replicas with CA
3. upgrade to ipa-4.2.0-15.el7_2.17 if older version was used for install
4. "ldapsearch -H $LDAP_URI -b cn=masters,cn=ipa,cn=etc,$BASEDN '(&(cn=CA)(ipaConfigString=caRenewalMaster))'" must return exactly one entry
Comment 7 Nikhil Dehadrai 2016-06-01 09:45:51 UTC 
IPA server version: ipa-server-4.2.0-15.el7_2.17.x86_64

1. Verified that only one entry is returned on executing the command mentioned inside Comment#6.
2. Refer the attachment for console output.

Thus marking the status of bug to "VERIFIED".
Comment 8 Nikhil Dehadrai 2016-06-01 09:46:50 UTC 
Created attachment 1163562 [details]
Bug Verification console output

Bug Verification console output steps.
Comment 12 errata-xmlrpc 2016-06-23 16:32:04 UTC 
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://access.redhat.com/errata/RHBA-2016:1256
Note You need to log in before you can comment on or make changes to this bug.