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:


We have very often this situation at customer configs:


- conflict on user entry:

nsuniqueid=dc5a4415-905211e6-aebbea4a-46cc96c4+uid=wcp6804,cn=users,cn=accounts,dc=psop,dc=be"

we unlink the entry (managed entries) to delete it definitively and:

ldapdelete -D "cn=directory manager" -W "nsuniqueid=dc5a4415-905211e6-aebbea4a-46cc96c4+uid=wcp6804,cn=users,cn=accounts,dc=psop,dc=be"
Enter LDAP Password: 
ldap_delete: Operations error (1)


We set internal ops log level and plugin error log to see:

[08/Feb/2017:09:42:35.033756579 +0100] referint-plugin - _update_one_value: entry cn=ipausers,cn=groups,cn=accounts,dc=psop,dc=be: deleting "member: nsuniqueid=dc5a4415-905211e6-aebbea4a-46cc96c4+uid=wcp6804,cn=users,cn=accounts,dc=psop,dc=be" failed (16)

there's no member of ipausers with the conflict. There's only the real entry.

But the entry to delete is memberof.

So, the only workaround is to disable referential integrity plugin.

The bug here is that the integrity is not there at adding the conflict. Why to check it at deleting it ?

Regards,

German

Per IPA triage, this is a DS bug. That said IPA team team needs to find time to create a tool for automatic fixing of most common replication issues (which can be fixed automatically based on IPA context/knowledge).

closing as a dup of bz 1274430 as per ds dev meeting / bug council/review

*** This bug has been marked as a duplicate of bug 1274430 ***