Bug 10788 - samba-tool ldapcmp reports differences for non-replicated attributes
Summary: samba-tool ldapcmp reports differences for non-replicated attributes
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.1.4
Hardware: All All
: P5 normal (vote)
Target Milestone: 4.3
Assignee: Stefan Metzmacher
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-27 13:13 UTC by Stefan Metzmacher
Modified: 2020-12-14 22:05 UTC (History)
3 users (show)

See Also:

Attachments
Possible patch for master (4.56 KB, patch)
2014-08-27 13:15 UTC, Stefan Metzmacher 		no flags Details
Patch for v4-1-test (4.80 KB, patch)
2014-09-02 08:14 UTC, Stefan Metzmacher 		metze: review? (abartlet)
 Details
Patch for v4-0-test (4.80 KB, patch)
2014-09-02 08:14 UTC, Stefan Metzmacher 		metze: review? (abartlet)
 Details
View All 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 Stefan Metzmacher 2014-08-27 13:13:21 UTC 
samba-tool ldapcmp reports differences for non-replicated attributes
Comment 1 Stefan Metzmacher 2014-08-27 13:15:20 UTC 
Created attachment 10234 [details]
Possible patch for master
Comment 2 Stefan Metzmacher 2014-09-02 08:14:00 UTC 
Created attachment 10246 [details]
Patch for v4-1-test
Comment 3 Stefan Metzmacher 2014-09-02 08:14:39 UTC 
Created attachment 10247 [details]
Patch for v4-0-test
Comment 4 heupink 2014-09-16 17:50:30 UTC 
After we upgraded from 4.1.11 to 4.1.12, and suddenly we're getting many ldapcmp failures on the attribute 'whenChanged'. In 4.1.11 life was good, and ldapcmp reported no differences at all.

In the patch it says:
+                # "whenChanged", # This is implicitly replicated

If I remove that comment sign, ldapcmp finishes successful again.

Should that comment sign be there? I have verified that, when changing a DN, the changes ARE replicated, but 'whenChanged' is still a little bit different on all three DC's.

Comparing before modification:
'CN=podcast,CN=Users,DC=samba,DC=company,DC=com' [ldap://dc2]
'CN=podcast,CN=Users,DC=samba,DC=company,DC=com' [ldap://dc4]
    Difference in attribute values:
        whenChanged =>
['20140507142704.0Z']
['20140826123226.0Z']
    FAILED 

After modification:
'CN=podcast,CN=Users,DC=samba,DC=merit,DC=unu,DC=edu' [ldap://dc2]
'CN=podcast,CN=Users,DC=samba,DC=merit,DC=unu,DC=edu' [ldap://dc4]
    Difference in attribute values:
        whenChanged =>.
['20140916171503.0Z']
['20140916171443.0Z']
    FAILED
Comment 5 Andreas Schneider 2014-10-28 10:25:57 UTC 
Ping Andrew!
Comment 6 Karolin Seeger 2014-11-27 10:59:25 UTC 
Is this a showstopper for 4.2.0?
Comment 7 Björn Jacke 2014-11-27 15:59:14 UTC 
no regresson, no blocker. please use milestones if you want to point out a target for the implementation.
Comment 8 Douglas Bagnall 2020-12-14 22:05:18 UTC 
Patch went in as eee14f775e6f2075729d68fa9598dd99f9b9b05d