Bug 49980 - Reject When Syncing from UCS to AD "ENTRY EXISTS"
Reject When Syncing from UCS to AD "ENTRY EXISTS"
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-08 14:58 CEST by Christian Völker
Modified: 2021-05-14 16:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019072921000494
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-08-08 14:58:42 CEST
Syncing a computer account from UCS (4.4-1) to AD gets rejected due to ENTRY EXISTS.
Logfile entries and further details in following (private) comments.

Somehow I have the impression it might have to do something with upper/ lower case...
Comment 4 Arvid Requate univentionstaff 2019-08-08 22:51:47 CEST
Maybe talk with Nico, he had something similar sounding at Ticket#: 2019062721000651. In that case there where deleted objects that still held the account name that was to be added. If the ltb-tools package is not installed then it's a bit tricky to search for the deleted objects in AD, something linke this:

ldapsearch -x -h "$(ucr get connector/ad/ldap/host)" -p 389 \
           -D "$(ucr get connector/ad/ldap/binddn)" \
           -y "$(ucr get connector/ad/ldap/bindpw)" \
           -E 1.2.840.113556.1.4.417 isDeleted=TRUE
Comment 5 Ingo Steuwer univentionstaff 2021-05-14 15:13:16 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.