Bug 11377 - samba classicupgrade does not create proper idmap.ldb records
Summary: samba classicupgrade does not create proper idmap.ldb records
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.2.2
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
: 9524 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-07-02 13:16 UTC by Yuriy Tabolin
Modified: 2021-12-08 01:17 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuriy Tabolin 2015-07-02 13:16:29 UTC
I have migrated my old samba 3.6 NT domain to samba 4.2.2 with samba-tool classicupgrade. After I run sysvolcheck and see error:
# samba-tool ntacl sysvolcheck
ERROR(<type 'exceptions.TypeError'>): uncaught exception - (87, 'Attribute not found')
File "/usr/local/lib/python2.7/site-packages/samba/netcmd/init.py", line 175, in _run
return self.run(*args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/samba/netcmd/ntacl.py", line 249, in run
lp)
File "/usr/local/lib/python2.7/site-packages/samba/provision/init.py", line 1717, in checksysvolacl
fsacl = getntacl(lp, dir_path, direct_db_access=direct_db_access, service=SYSVOL_SERVICE)
File "/usr/local/lib/python2.7/site-packages/samba/ntacls.py", line 73, in getntacl
xattr.XATTR_NTACL_NAME)

I see too few records in idmap.ldb:
#tdbtool /var/db/samba4/private/idmap.ldb
tdb> info
...
Number of records: 12
...

Because of this, sysvolreset doesn't work and I cannot assign properly fs ACL to sysvol. This looks like a bug.
Comment 1 Björn Jacke 2021-12-07 22:42:28 UTC
I've made numerous "classicupgrade" migrations and never ran into such a problem. Maybe you needed to start samba at least once.
Comment 2 Björn Jacke 2021-12-08 01:17:16 UTC
*** Bug 9524 has been marked as a duplicate of this bug. ***