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.
DescriptionNikhil Dehadrai
2018-06-29 10:28:17 UTC
Description of problem:
ipa-replica-install --setup-kra broken on DL0 with latest version
Version-Release number of selected component (if applicable):
ipa-server-4.6.4-2.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Setup IPA at DL0
2. Setup Replica with KRA at DL0
3. Check ipareplica-install.log
Actual results:
ipa-replica installation fails
Expected results:
ipa-replica-installation with KRA should be successful
Additional info:
The issue is not observed in RHEL75z testing
Comment 6Florence Blanc-Renaud
2018-07-10 05:09:29 UTC
Comment 7Florence Blanc-Renaud
2018-07-30 16:02:32 UTC
Bug analysis
------------
Valid bug: yes
Regression: yes
Regression introduction: 389-ds-base-1.3.7 with the 389-ds patch for https://pagure.io/389-ds-base/issue/49599
Affected versions: RHEL 7.6
Use cases (reproduction steps):
* install replica with KRA in domain level 0:
** install ipa server in dl 0 with ca and kra (--domain-level 0 --setup-kra)
** prepare replica with ipa-replica-prepare
** install replica with ipa-replica-install --setup-ca --setup-kra /path/to/replica-file
Cause: pkispawn is failing when configuring the replication for CA.
During repl setup, pkispawn is reading the attribute nsds5replicaLastInitStatus in cn=masterAgreement1-$hostname-pki-tomcat,cn=replica,cn=o\3Dipaca,cn=mapping tree,cn=config in order to find the replication status.
The new format (in 389-ds-base-1.3.7) for this attribute is "Error (0) Total update succeeded" but pkispawn is expecting "0 Total update succeeded" (see https://github.com/dogtagpki/pki/blob/DOGTAG_10_5_BRANCH/base/server/cms/src/com/netscape/cms/servlet/csadmin/ConfigurationUtils.java#L2028).
Consequence: ipa-server-install fails in pkispawn step.
Workaround: None
Due to the above analysis, I am moving this issue to pki-core component.
Comment 8Alexander Bokovoy
2018-08-02 07:44:10 UTC
Thanks Alexander; patches merged:
master: 8147769f8bc8a41afa77dfcd97464dc736d61935
DOGTAG_10_5_BRANCH: 151ecf63106425cada104d141a81722570ba2b28
I guess we need to collect some ACKs and then someone (Matt?)
will build a build.
ipa-server: ipa-4.6.4.5.el7
Verified that the ipa-replica-installation with KRA at DL0 is successful and the error mentioned in bug is no more observed.
Thus marking the status of bug to 'VERIFIED'.
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-2018:3195