Bug 38445 – remove_s4_rejected.py should remove DN from 'S4 GUID' table

Bug 38445 - remove_s4_rejected.py should remove DN from 'S4 GUID' table


Summary:	remove_s4_rejected.py should remove DN from 'S4 GUID' table

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-05-05 16:42 CEST by Janis Meybohm
Modified:	2021-05-03 21:29 CEST (History)
CC List:	4 users (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?:	2: Will only affect a few 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.069
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2015042921000345, 2019050721000314
Bug group (optional):
Max CVSS v3 score:

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 Janis Meybohm

2015-05-05 16:42:25 CEST

Ticket#2015042921000345

remove_s4_rejected.py only removes the given reject DN from 'S4 rejected' table. It should also remove corresponding rows from 'S4 GUID' table.

DELETE FROM 'S4 GUID' WHERE value='%s'" % s4_dn

Comment 1 Janis Meybohm

2015-05-05 16:46:09 CEST

Got that wrong. 'value' in 'S4 GUID' does contain possible old-dns (moves objects) so one would need to delete by GUID ('key') I think.

Comment 2 Stefan Gohmann

2019-01-03 07:17:30 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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

Comment 3 Arvid Requate

2019-05-16 17:53:33 CEST

I just had this again in a support case (Ticket#2019050721000314) and it was a bit tedious to clean up the 'S4 GUID' table. In that case (Bug #49498), without the cleanup, a resync_from_s4 woult find an old, invalid DN in that table and would try to to rename a noexistant DN in OpenLDAP, resulting in the next reject.