Implement retry with backoff when key replication fails for some reason.
Note that various situations (e.g. LDAP disconnect/reconnect or LDAPMOD replicated from another clone) cause authority to be reinitialised. In this case, existing "KeyReplicatorRunner-<id>" thread should be detected and either a) left alone or b) killed and restarted (i.e. we must avoid multiple replicator threads for a single authority)
Pushed to master:
f78af863edb020db763ce7920b3b0a6ea61d8e5e Retry failed key retrieval with backoff 9062e0265e7cadfa05f64a7c5c0a718594283d06 Don't update obsolete CertificateAuthority after key retrieval b1bafc4935c088fe98373a7988f5e0518b950226 Limit key retrieval to a single thread per CA
Metadata Update from @ftweedal: - Issue assigned to ftweedal - Issue set to the milestone: 10.3.2
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/2413
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.