Windows Sync total update fails if OU is in the 389 side.

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48841

• Created at 2016-05-18 02:09:58 by nhosoi (@nhosoi)
• Closed at 2020-04-01 17:36:49 as wontfix
• Assigned to nobody

---

My lab environment: 389-ds-base 1.3.4.8 + win 2012 r2

OU just in 389 side with users: Full sync failed, log error:

[17/May/2016:14:19:44 -0300] - Attempting to add entry cn=mais um teste,ou=teste,ou=RNP,dc=homolog,dc=rnp to AD for local entry uid=teste.teste,ou=teste,ou=RNP,dc=homolog,dc=rnp
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Received result code 32 (0000208D: NameErr: DSID-03100238, problem 2001 (NO_OBJECT), data 0, best match of:   'OU=RNP,DC=homolog,DC=rnp' ) for add operation
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): windows_process_total_add: Cannot replay add operation.
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Beginning linger on the connection
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): windows_tot_run: failed to obtain data to send to the consumer; LDAP error - 1
[17/May/2016:14:19:44 -0300] - Calling dirsync search request plugin
[17/May/2016:14:19:44 -0300] - Sending dirsync search request
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Cancelling linger on the connection
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Disconnected from the consumer
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - windows_inc_runs: cancelled dirsync: 7fa660001d60, rval: 1

OU just in AD side with users: Full sync ok

My production environment: 389-ds-base 1.3.2.19 + win 2008 r2

OU just in 389 side with users: Full sync ok OU just in AD side with users: Full sync ok

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 23:01:02

Metadata Update from @nhosoi:

• Issue set to the milestone: 1.3.6 backlog

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:05:45

Metadata Update from @mreynolds389:

• Issue close_status updated to: None
• Issue set to the milestone: FUTURE (was: 1.3.6 backlog)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-04-01 17:36:50

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None
• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)