See https://pagure.io/freeipa/issue/7815#comment-547193 for original analysis.
In brief, if CRLIP gets disabled, then later re-enabled, via caadmin interface (or other online interface), it will not refresh CRL data from LDAP. If some other clone was generating CRLs in the meantime, the CRL number will be wrong.
The CRLIP must reload the latest CRL from LDAP when it gets reinitialised.
Metadata Update from @ftweedal: - Issue assigned to ftweedal
PR: https://github.com/dogtagpki/pki/pull/138
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
Merged to master:
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/3202
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.