https://bugzilla.redhat.com/show_bug.cgi?id=804198 (Red Hat Directory Server)
Description of problem: If an entry is moved to an ou outside of the scope of the WinSync agreement, then subsequently returned to the scope (for example, an employee that has left and returned), they are not synchronized back to the RHDS side of the agreement Version-Release number of selected component (if applicable): RHDS 9.0 How reproducible: Everey time Steps to Reproduce: 1. Move an object from within the scope of the WinSync agreement to outside of the scope 2. Wait for the object to disappear from the RHDS side 3. Move object back to the OU it was in originally Actual results: object is not synchronized to RHDS Expected results: object is synchronized to RHDS Additional info:
Could not reproduce with latest 1.2.11 code - steps:
on AD, create cn=Test container under suffix under cn=Test, create a cn=active users and a cn=deleted users container
Do the same on DS
Set up sync agreement to sync AD cn=active users,cn=Test,suffix with DS cn=active users,ou=people,suffix
Note: cn=deleted users,cn=Test and cn=deleted users,ou=People are outside the scope of the sync area
Add some users to both sides, confirm sync is working
On AD, move (rename or modrdn) a user from cn=active users,cn=Test,suffix to newsuperior cn=deleted users,cn=Test,suffix
wait for sync to happen
confirm on DS that the user is no longer in cn=active users,ou=People,suffix
on AD, move the user back to cn=active users,cn=Test,suffix
confirm on DS that the user is back in cn=active users,ou=People,suffix
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.11.rc1
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/323
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: Invalid)
Login to comment on this ticket.