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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3805

I update to F18 my old ipa server that has been upgraded since F15.

It has stil a separate directory instance for the CA.

When certmonger decided to renrew the CA certificate renew_ca_cert failed to update the CA instance users with the renewd certs.

the reason is that renew_ca_cert tried to perform all its operations against the main IPA instance and not the CA instanace on port 7389 where these objects actually are.
all renew_ca_cert operation terminated with 'no such entry' until certmonger failed to update certs as the RA certificate didn't match the cA user anymore.

*** Bug 986461 has been marked as a duplicate of this bug. ***

I have just verified that this bug in fact does *not* affect RHEL 6.4. It only affects installs updated from Dogtag 9 to Dogtag 10.

Thank you, I will close the bug then.