Univention Bugzilla – Bug 42383
purge_s4_computer.py does not remove all SRV records
Last modified: 2020-07-03 20:56:42 CEST
I deleted two UCS Backups (Samba AD DCs) with purge_s4_computer.py: > /usr/share/univention-samba4/scripts/purge_s4_computer.py --computername=ucs02 > /usr/share/univention-samba4/scripts/purge_s4_computer.py --computername=ucs03 Afterwards, the following leftovers are still present: > root@ucs01:~# dig @localhost $(ucr get domainname) axfr | grep -i -E 'ucs02|ucs03' > [...] > _ldap._tcp.ForestDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs02.abcd.example.org. > _ldap._tcp.ForestDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs03.abcd.example.org. > _ldap._tcp.DomainDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs02.abcd.example.org. > _ldap._tcp.DomainDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs03.abcd.example.org. > _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs02.abcd.example.org. > _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs03.abcd.example.org. > _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs02.abcd.example.org. > _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.abcd.example.org. 900 IN SRV 0 100 389 ucs03.abcd.example.org. They should be removed as well.
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Seen also during a workshop with univention-samba4 7.0.2-27. Note: the original object to delete was stored in lower case like "ucs02" in the directory, while the command to delete was /usr/share/univention-samba4/scripts/purge_s4_computer.py --computername=UCS02 The main reason to use the name in uppercase was because the description suggests to use "--computername=COMPUTERNAME" We also removed another system, this time by using "--computername=ucs3". In this case all SRV records have been removed successfully.
This issue has been filed against UCS 4.2. UCS 4.2 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.