Bug 44893 - purge_s4_computer.py should also delete all references in Samba/AD if the udm object does not exist anymore
purge_s4_computer.py should also delete all references in Samba/AD if the udm...
Status: NEW
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-29 12:22 CEST by Michael Grandjean
Modified: 2020-06-22 18:29 CEST (History)
2 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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Michael Grandjean univentionstaff 2017-06-29 12:22:40 CEST
Scenario: A UCS Backup/Slave with Samba AD has been deleted via UMC/UDM. 

This leaves references in the Samba AD directory. Unfortunately "purge_s4_computer.py" aborts, because it can't find the object in OpenLDAP. It should nevertheless be possible to get rid of the object and references in Samba AD, even if the object does not exist in OpenLDAP anymore.

I guess it's not that trivial to find all correct entries if we only know the hostname. Maybe the tool should list all findings and ask the user to confirm the deletion (similiar to samba-tool dbcheck --fix)?
Comment 1 Arvid Requate univentionstaff 2017-07-03 16:15:07 CEST
My take on this would be to recommend samba-tool domain demote (e.g. with the option --remove-other-dead-server). I think we should adjust purge_s4_computer.py to make use of that.