diff options
| author | Stefan Metzmacher <metze@samba.org> | 2019-03-11 14:52:57 +0100 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2019-03-28 12:19:12 +0000 |
| commit | f91050ee547ff645933da1a3ceeecf3d1052045e (patch) | |
| tree | 819299efeaa01415dcee92f280144315d3d86808 /selftest | |
| parent | 833d543717ca7f59270a384397dd5a15d3ab79ae (diff) | |
| download | samba-f91050ee547ff645933da1a3ceeecf3d1052045e.tar.gz | |
blackbox/dbcheck-links.sh: reproduce lost deleted object problem
When a parent object is removed during the tombstone garbage collection
before a child object and samba-tool dbcheck runs at the same time, the
following can happen:
- If the object child had DISALLOW_MOVE_ON_DELETE in systemFlags,
samba-tool dbcheck moves the object under the LostAndFound[Config]
object (as an originating update!)
- The lastKnownParent attribute is removed (as an originating update!)
These originating updates cause the object to have an extended time
as tombstone. And these changes are replicated to other DCs,
which very likely already removed the object completely!
This means the destination DC of replication has no chance to handle
the object it gets from the source DC with just 2 attributes (name, lastKnownParent).
The destination logs something like:
No objectClass found in replPropertyMetaData
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13816
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
(cherry picked from commit 5357f591accffbf8c62335c308b985811b66f0b5)
Diffstat (limited to 'selftest')
| -rw-r--r-- | selftest/knownfail.d/dbcheck-list-deleted | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/selftest/knownfail.d/dbcheck-list-deleted b/selftest/knownfail.d/dbcheck-list-deleted new file mode 100644 index 00000000000..676281faba5 --- /dev/null +++ b/selftest/knownfail.d/dbcheck-list-deleted @@ -0,0 +1,2 @@ +^samba4.blackbox.dbcheck-links.release-4-5-0-pre1.dbcheck_lost_deleted_user1 +^samba4.blackbox.dbcheck-links.release-4-5-0-pre1.lost_deleted_user1_clean_A |