During a MODRDN of a member, referential integrity will update the groups containing this member. Under specific conditions, the MODRDN can fail (err=1) and the updated groups leave untouched because of the txn abort.
The conditions are:
This bug may look like mystery failure.
Indeed there is no reported failure (plugin or internal op) because this is just a wrong returned code that is returned. Also because of the specific conditions it looks like random issue why a given MODRDN succeeds and an other fails. Finally when the MODRDN fails, a second attempt of the same MODRDN will succeed. In fact the DB is unchanged but the first attempt reordered the member values in the entry cache. The target entry (of the MODRDN) becomes the last value of the group.
All versions/platform
Reproducible TC attached
MODRDN fails
MODRDN should succeeds
Metadata Update from @tbordaz: - Issue assigned to tbordaz
https://pagure.io/389-ds-base/pull-request/50021
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @tbordaz: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1648922
Issue linked to Bugzilla: Bug 1648922
ce05f24..5284dce master
Metadata Update from @tbordaz: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Please backport to 1.3.9 and 1.3.8
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.8 (was: 0.0 NEEDS_TRIAGE)
e68ffaa..9740c20 389-ds-base-1.3.9 0a2cc3b..3800388 389-ds-base-1.3.8
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3079
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. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.