Customer is creating and deleting same replica several times. As a result, there's an issue to create a replica with a failure of pki instance configuration.
One of the observed issues is:
# certificateRepository, ca, ipaca dn: ou=certificateRepository,ou=ca,o=ipaca nextRange: 140000001 nextRange: 350000001 nextRange: 340000001
I am sorry that I don't know exactly how to reproduce this. I report this bug just to trace this behavior that is apparently not desired.
The real error is in an attachment to the associated bug, and it's related to the creation of a range that is rejected with err=68 (entry already exists).
The debug log showing this error and also, the full list of ranges (objectclass=pkirange) are also attached to the associated bug.
Any help to understand why the range creation is failing is welcome.
Per CS/DS Triage Meeting of 03/22/2016: 10.4
It was determined that the ability to replicate this issue contained insufficient data.
Closing ticket as wontfix.
Metadata Update from @mharmsen: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: wontfix (was: Invalid)
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/2351
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.