sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-02-04 17:47:26 +03:00
Code
samba-mirror/selftest/knownfail.d/replica_sync

9 lines
996 B
Plaintext
Raw Normal View History

selftest: Windows resolves object conflicts differently to Samba While testing link conflicts I noticed that Windows resolves conflicts differently to Samba. Samba considers the version number first when resolving the conflict, whereas Windows always takes the latest change. The existing object conflict test cases didn't detect this problem because they were both modifying the object the same number of times (so they had the same version number). I've added new tests that highlight the problem. They are basically the same as the existing rename tests, except that only one DC does the rename. Samba will always pick the renamed object as the winner, whereas Windows picks the most recent change. I've marked this test as a known fail for now. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13039 Signed-off-by: Tim Beale <timbeale@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
2017-09-26 13:11:47 +13:00
# Samba currently picks a different winner of object conflicts compared to Windows.
# Samba uses the version number whereas Windows always takes the most recent change
samba4.drs.replica_sync.python\(vampire_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRenamedVsNewRemoteWin\(vampire_dc:local\)
samba4.drs.replica_sync.python\(promoted_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRenamedVsNewRemoteWin\(promoted_dc:local\)
samba4.drs.replica_sync.python\(vampire_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRenamedVsNewLocalWin\(vampire_dc:local\)
samba4.drs.replica_sync.python\(promoted_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplConflictsRenamedVsNewLocalWin\(promoted_dc:local\)
selftest: Add test for a re-animated object conflict Added a test to simulate a user accidentally being deleted and 2 different admins trying to resolve the problem simultaneously - one by re-animating the object and one by just creating a new object with the same name. Currently this test fails on Samba because it chooses the higher version number as the winner instead of the latest change. BUG: https://bugzilla.samba.org/show_bug.cgi?id=13039 Signed-off-by: Tim Beale <timbeale@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org> Reviewed-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz>
2017-09-20 17:29:46 +12:00
samba4.drs.replica_sync.python\(vampire_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplReanimationConflict\(vampire_dc:local\)
samba4.drs.replica_sync.python\(promoted_dc\).replica_sync.DrsReplicaSyncTestCase.test_ReplReanimationConflict\(promoted_dc:local\)
Copy Permalink