The resolution for issue https://pagure.io/dogtagpki/issue/2654 caused a regression in lightweight CA replication. When the authorityMonitor encounters a CA whose keys are not present, signingUnit initialisation expectedly fails. The behaviour introduced in commit 4551eb1ce6b14e4a37f9c70b3bfd6c9050e13f10 then results in a NullPointerException, crashing the authorityMonitor thread.
Steps to Reproduce:
1. install IPA master and replica, both with CA role 2. create LWCA on one master
Actual results:
- Observe authorityMonitor thread crash via `journalctl -u pki-tomcatd@pki-tomcat`, caused by NullPointerException - Observe that LWCA replication fails.
Expected results:
- No authorityMonitor thread crash. - LWCA key replication succeeds
Metadata Update from @mharmsen: - 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1543242 - Custom field type adjusted to None - Custom field version adjusted to None
Whups, I forgot to link to https://pagure.io/dogtagpki/issue/2929 in the BZ Devel Whiteboard field. This is a duplicate.
Metadata Update from @ftweedal: - Issue close_status updated to: duplicate
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.6 (was: 10.5)
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/3051
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.