Bug 14669 - Backup using samba-tool domain backup requires ridNextRid on the source DC
Summary: Backup using samba-tool domain backup requires ridNextRid on the source DC
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.14.0
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Jennifer Sutton
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks: 14743
  Show dependency tree / graph
 
Reported: 2021-03-12 18:26 UTC by Andrew Bartlett
Modified: 2021-11-25 17:04 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bartlett 2021-03-12 18:26:06 UTC 
The samba-tool domain backup code requires that the source domain controller already have a ridNextRid attribute, which is currently only populated for one the first user is created on that DC.

The algorithm for creating the ridNextRid is known, and the dbcheck code (python/samba/dbchecker.py) already has that code.  If this was shared, a 'virtual' ridNextRid could be calculated, removing this restriction.
Comment 1 Samba QA Contact 2021-06-11 08:29:12 UTC 
This bug was referenced in samba master:

e8c242bed19432d96e78dc345ab5f06422c5b104
658e5a6cc20b57f48477affd370fe25458178b92
b7e6a1c5da7283c49586dc29f85ab19e0e57b0f6
cc98e03e7a0f2bf7a1ace2950fe6500f53640c1b
7c7cad81844950c3efe9a540a47b9d4e1ce1b2a1
59d293b60608172ae61551c642d13d3b215924e4
Comment 2 Samba QA Contact 2021-07-12 13:53:45 UTC 
This bug was referenced in samba v4-14-test:

79029224ee02ff9f240ab1a81a3372a193b0879d
b226e83a3dc3c74c06e48469ec02c19cbbfb963b
f9d2652a0b42c37acff3ce16f0c430f3522012e5
94ca97bd121993b461082286ae24d2510211d36e
69d8b64fdc1b2d9b5ac88385af704e2935d6ca4e
a6447a1dce1bed1a33ab6aa729f5837acc3895f6
Comment 3 Samba QA Contact 2021-07-13 10:34:12 UTC 
This bug was referenced in samba v4-14-stable (Release samba-4.14.6):

79029224ee02ff9f240ab1a81a3372a193b0879d
b226e83a3dc3c74c06e48469ec02c19cbbfb963b
f9d2652a0b42c37acff3ce16f0c430f3522012e5
94ca97bd121993b461082286ae24d2510211d36e
69d8b64fdc1b2d9b5ac88385af704e2935d6ca4e
a6447a1dce1bed1a33ab6aa729f5837acc3895f6
Comment 4 Samba QA Contact 2021-07-13 13:19:13 UTC 
This bug was referenced in samba v4-13-test:

445fb770c77b488c3ff7e426d985206967f5d825
00444ac64f5b9ece88a62100b9b98c6fe75f6a60
b3d59842fd99c8d72dbc6f65259efad05bd5d897
afad2fd9e2499f6ddacae9ddace22c81e9de7da0
e5c3a675464208bffad08a0e923406c9a2d4b0a5
82e0f3e79975ffdffd5afca77b6458a33488eff7
Comment 5 Samba QA Contact 2021-07-14 08:16:36 UTC 
This bug was referenced in samba v4-13-stable (Release samba-4.13.10):

445fb770c77b488c3ff7e426d985206967f5d825
00444ac64f5b9ece88a62100b9b98c6fe75f6a60
b3d59842fd99c8d72dbc6f65259efad05bd5d897
afad2fd9e2499f6ddacae9ddace22c81e9de7da0
e5c3a675464208bffad08a0e923406c9a2d4b0a5
82e0f3e79975ffdffd5afca77b6458a33488eff7