Clone of https://bugzilla.redhat.com/show_bug.cgi?id=1638379.
The PKI fails to start when we have replication conflicts in ou=certificateprofiles,ou=ca,o=ipaca subtree. LDAP conflict entries will add to the operational LDAP attribute 'numSubordinates'. As a result the number of actual cert profiles and leaf entries is this subtree is different.
The RfE is to not depend on the operational attribute for a successful PKI initialization.
Note that a similar mechanism is used for the LDAPProfileSubsystem and the CertificateAuthority monitor thread for loading LWCAs at startup. The issue should be addressed in both places.
Metadata Update from @ftweedal: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @ftweedal: - Issue assigned to ftweedal
PR: https://github.com/dogtagpki/pki/pull/188
pushed to master:
DOGTAG_10_6_BRANCH:
DOGTAG_10_6_BRANCH
DOGTAG_10_5_BRANCH:
DOGTAG_10_5_BRANCH
Closing fixed.
Metadata Update from @ftweedal: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3195
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.