#50236 memberOf modrdn should be more robust
Closed: wontfix by mreynolds. Opened by mreynolds.

Issue Description

When there are already heavily nested group membership, and you perform a modrdn, it is possible that entry was already a memberOf a group. This results in the operation failing because of error 20 (type or value already exists). In this case the error 20 should be ignored.

Due to a coding mistake the error 20 was also incorrectly converted into an error 1

Package Version and Platform

Affects 1.3.9 and up


https://pagure.io/389-ds-base/pull-request/50237

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: review)
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1680245

commit 47c42590e5ba8b97259445f8892023dfdbe58723

f19f27931..ea24c43a9 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

eee97e69f..70117f568 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Is there a plan to backport these fixes also to fedora?
because current version in f28 and f29 are affected ATM.

Is there a plan to backport these fixes also to fedora?
because current version in f28 and f29 are affected ATM.

Yup I will be doing upstream builds soon(tomorrow?). I want to get a UI patch in first, then I will do the builds...

Yup I will be doing updartream builds soon(tomorrow?). I want to get a UI patch in first, then I will do the builds...

No hurry if you need other fixes. I just wanted to be sure that it will not in in few months :-)

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/3295

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata