Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
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 attachment and it's related to the creation of a range that is rejected with err=68 (entry already exists).
I am attaching the debug log showing this error. And also, the full list of ranges (objectclass=pkirange)
Any help to understand why the range creation is failing is welcome.
Thanks and regards
German.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Hi Matthew,
Thanks. The customer has reinstalled from scratch. And I don't think this bug is easy to reproduce. So, no need to be back-ported.
Thanks a lot for the fix and your help.
Regards,
German.
On Mar 21, 2016, at 22:49, Matthew Harmsen <mharmsen> wrote:
> German,
>
> Once the following Bug has been fixed:
>
> Bugzilla Bug #1311251 - Multiple nextRange attributes in ou=certificateRepository,ou=ca,o=ipaca
>
> Does the customer require that the solution be back-ported to RHEL 7.2.z?
>
> Thanks,
> -- Matt
Per CS/DS Triage Meeting of 03/22/2016: 10.4