New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memberOf modrdn should be more robust #3295
Comments
Comment from mreynolds (@mreynolds389) at 2019-02-21 23:03:02 |
Comment from mreynolds (@mreynolds389) at 2019-02-21 23:03:03 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2019-02-23 13:15:37 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2019-02-26 15:29:57 commit 47c4259 |
Comment from mreynolds (@mreynolds389) at 2019-02-26 15:29:58 Metadata Update from @mreynolds389:
|
Comment from lslebodn at 2019-02-26 15:58:35 Is there a plan to backport these fixes also to fedora? |
Comment from mreynolds (@mreynolds389) at 2019-02-26 16:01:11
Yup I will be doing upstream builds soon(tomorrow?). I want to get a UI patch in first, then I will do the builds... |
Comment from lslebodn at 2019-02-26 17:21:18
No hurry if you need other fixes. I just wanted to be sure that it will not in in few months :-) |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50236
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
The text was updated successfully, but these errors were encountered: