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 1829993 - Sub-CA key replication failure [rhel-7.6.z]
Summary: Sub-CA key replication failure [rhel-7.6.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.7
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1755223 1756913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-30 17:12 UTC by Jaroslav Reznik
Modified: 2020-05-06 12:17 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1756913
Environment:
Last Closed: 2020-05-06 12:17:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4170 0 None None None 2020-05-06 12:17:40 UTC

Comment 2 Nikhil Dehadrai 2020-05-04 05:27:07 UTC
This bug is clone of bug BZ#1756913

Thus as per comment at https://bugzilla.redhat.com/show_bug.cgi?id=1756913#c4, verifying the bug as follows.



Bugzilla has been verified manually using the below steps 

[root@master alias]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 (Maipo)
ipa-server-4.6.4-10.el7_6.9.x86_64
389-ds-base-1.3.8.4-25.1.el7_6.x86_64
pki-ca-10.5.9-13.el7_6.noarch

1. install master
2. install replica with CA
3. create a sub-CA on one server (e.g master)

#ipa ca-add test_subca --subject='cn=test_subca'
#ipa ca-find
[root@master alias]# ipa ca-find
  Name: test_subca
  Authority ID: b6edadc5-adc2-4245-8ad5-56fef2963eb6
  Subject DN: CN=test_subca
  Issuer DN: CN=Certificate Authority,O=RHEL76.TEST

4. Check the sub-CA signing keys on master.
[root@master alias]# pwd
/var/lib/pki/pki-tomcat/alias
[root@master alias]# certutil -d . -L
Certificate Nickname                                         Trust Attributes
                                                             SSL,S/MIME,JAR/XPI
caSigningCert cert-pki-ca b6edadc5-adc2-4245-8ad5-56fef2963eb6 u,u,u

5. confirm that after a short time (10 seconds ought to do it), the sub-CA signing keys
   appear in the Dogtag NSSDB on the OTHER server
   (certutil -d /etc/pki/pki-tomcat/alias -L)
[root@replica alias]# certutil -d . -L
caSigningCert cert-pki-ca b6edadc5-adc2-4245-8ad5-56fef2963eb6 u,u,u

Hence marking the bug as VERIFIED.

Comment 5 errata-xmlrpc 2020-05-06 12:17:38 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-2019:4170


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