#49386 Memberof should be ignore MODRDN when the pre/post entry are identical
Closed: wontfix Opened by tbordaz.

Issue Description

For the following request, memberof will remove the pre-entry from entries referring to it (groups that it is member and members it contains) and add the post-entry to the same entries. All this is useless because the entry keeps its DN unchanged

MODRDN dn="uid=foo,<suffix>" newrdn="uid=foo" newsuperior="<suffix>"

Package Version and Platform

all versions

Steps to reproduce

  1. modrdn with targetdn and dest_dn being identical

Actual results

memberof evaluates membership

Expected results

memberof should ignore the operation


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
- Issue set to the milestone: 1.3.7.0

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

Metadata Update from @tbordaz:
- Custom field origin adjusted to IPA (was: None)
- Custom field reviewstatus adjusted to review (was: None)
- Custom field type adjusted to defect (was: None)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

git push origin master

Counting objects: 11, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 3.27 KiB | 0 bytes/s, done.
Total 11 (delta 7), reused 0 (delta 0)
To ssh://git@pagure.io/389-ds-base.git
   e123acb..35c20ca  master -> master

git push origin 389-ds-base-1.3.7

Counting objects: 11, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 3.28 KiB | 0 bytes/s, done.
Total 11 (delta 7), reused 0 (delta 0)
To ssh://git@pagure.io/389-ds-base.git
   c7d13c2..9271d5c  389-ds-base-1.3.7 -> 389-ds-base-1.3.7

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

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