Bug 1506525

Summary: server-del doesn't remove dns-server configuration from ldap [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: ipaAssignee: Pavel Picka <ppicka>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.4CC: fbarreto, ipa-maint, ksiddiqu, msauton, ppicka, pvoborni, pvomacka, rcritten, tdudlak, tscherf
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ipa-4.5.0-22.el7_4 Doc Type: If docs needed, set a value
Doc Text:
Cause – Invocation of the ipa server-del <hostname> command. Consequence – There was still record in ldap if DNS was installed on the <hostname> server and it should not be. Fix – A method has been added to delete ldap records for <hostname> server into procedure of server-del command. Result – The <hostame> server record is being deleted and after running server-del command there is no record in ldap for this server.
 Story Points: ---
Clone Of: 1506188 Environment:
Last Closed: 2017-11-30 16:01:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1506188    
Bug Blocks:    
Attachments:
Description Flags
output none

Description Oneata Mircea Teodor 2017-10-26 09:35:12 UTC 
This bug has been copied from bug #1506188 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Petr Vobornik 2017-10-27 15:22:17 UTC 
master:
    063211d server.py: Removes dns-server configuration from ldap
ipa-4-5:
    005c928 server.py: Removes dns-server configuration from ldap
Comment 5 Pavel Picka 2017-11-08 12:53:40 UTC 
Created attachment 1349446 [details]
output

verified on 4.5.0-22.el7_4.x86_64
Comment 8 errata-xmlrpc 2017-11-30 16:01:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3319