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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/499
In the function urp_delete_operation, if to-be-deleted entry is found a tombstoned entry, the urp code is supposed to return -1 not to apply the delete in the backend code, but it should be treated as LDAP_SUCCESS not to return replay failure to the supplier. But the backend automatically sets -1 (Operation error) if the return value from the plugins.
I'm also concerned this error setting could cause the replication hang.
Comment by the author.
{{{
/*
* This operation won't be replayed. That is, this CSN won't update
* the max csn in RUV. The CSN is left uncommitted in RUV unless an
* error is set to op_result. Just to get rid of this CSN from RUV,
* setting an error to op_result
*/
/* op_result = LDAP_SUCCESS; */
}}}
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata). When the errata is created, the bugs should be automatically moved back to ON_QA.
Comment 3Sankar Ramalingam
2014-01-30 10:42:38 UTC
(In reply to Sankar Ramalingam from comment #3)
> Please add steps to verify bugzilla
URP (Update Resolution Procedure) is for handling conflicts. Due to the nature of the code, there is no easy "steps" to duplicate the original bug.
I'd suggest setting up 2-way MMR, repeat adding and deleting a same entry on each master. It'd generate conflicts. Run it for a while, e.g., one hour.
If the test runs without any problem AND
when the test is done, there is no odd entries such as a double nsuniqueid entry:
dn: nsuniqueid=<UNIQID>,nsuniqueid=<UNIQID>,<original_dn>,
then we can mark verified.
After an hour of repeated add/delete on uid=urptest,dc=passsync,dc=com entry
the log contained a lot of entries like these:
dn: nsuniqueid=1d51ab8c-9e0a11e3-b1d7b2f7-c7629fde+uid=urptest,dc=passsync,dc=com
dn: nsuniqueid=4114f182-9e0a11e3-b1d7b2f7-c7629fde+uid=urptest,dc=passsync,dc=com
No entries with double nsuniqueid were present in the directory.
Marking verified as per comment#4.
Comment 6Sankar Ramalingam
2014-04-23 03:59:57 UTC
There is no easy way to reproduce the exact problem. Hence, marking the bug with qe_test_coverage- flag.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.