Steps to reproduce: [0] Setup WinSync agreement with winSyncWindowsFilter: (sn=AD_sync*) [1] Add N users to AD with sn: AD_sync_N, AD_no_sync_N [2] Initialize replication agreement [3] AD_sync_N users should be synced to DS [4] Change winSyncWindowsFilter to (|(sn=AD_sync*)(sn=AD_no_sync*)) [5] Reinitialize replication agreement [6] AD_no_sync_N users should be synced to DS, but they're not. Additional info: After server restart and replica reinitialization new entries will sync to DS. Problem was found by Milan Kub?k: https://bugzilla.redhat.com/show_bug.cgi?id=746646#c13
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.7 backlog
Metadata Update from @mreynolds: - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - 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/1349
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.