Skip to content
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

Closed
389-ds-bot opened this issue Sep 13, 2020 · 8 comments
Closed

memberOf modrdn should be more robust #3295

389-ds-bot opened this issue Sep 13, 2020 · 8 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

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

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.9 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2019-02-21 23:03:02

#3296

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-02-21 23:03:03

Metadata Update from @mreynolds389:

  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to review

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-02-23 13:15:37

Metadata Update from @mreynolds389:

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-02-26 15:29:57

commit 47c4259

f19f279..ea24c43 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

eee97e6..70117f5 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-02-26 15:29:58

Metadata Update from @mreynolds389:

  • Issue close_status updated to: fixed
  • Issue status updated to: Closed (was: Open)

@389-ds-bot
Copy link
Author

Comment from lslebodn at 2019-02-26 15:58:35

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

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-02-26 16:01:11

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...

@389-ds-bot
Copy link
Author

Comment from lslebodn at 2019-02-26 17:21:18

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 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant