Bug 790931

Summary:	unable to remove ipa if another ds instance is setup
Product:	Red Hat Enterprise Linux 6	Reporter:	Michael Gregg <mgregg>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED ERRATA	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	mkosek, nsoman
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-2.2.0-4.el6	Doc Type:	Bug Fix
Doc Text:	No documentation needed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:18:46 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:

Description Michael Gregg 2012-02-15 18:30:44 UTC

Description of problem:
If ipa-server-install --uninstall is run before all other ds instances have been removed, you will break the current ipa install, and will be unable to either reinstall ipa, or, continue removing ipa.

Version-Release number of selected component (if applicable):
ipa-server-2.1.3-9.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. ipa-server-install (setup working ipa)
2. setup-ds.pl (setup a new ds instance on any available port)
3. ipa-server-install --uninstall
4. remove-ds.pl -i slapd-(step 2)
5. ipa-server-install --uninstall
  
Actual results:
[root@ipaqavmd ticket-278]# ipa-server-install --uninstall 
Are you sure you want to continue with the uninstall procedure? [no]: yes
Shutting down all IPA services
Removing IPA client configuration
Unconfiguring directory server
root        : ERROR    IPA cannot be re-installed without removing existing 389-ds instance(s)

[root@ipaqavmd ticket-278]# remove-ds.pl -i slapd-ipaqavmd
Instance slapd-ipaqavmd removed.

[root@ipaqavmd ticket-278]# ipa-server-install --uninstall 
Are you sure you want to continue with the uninstall procedure? [no]: yes
Shutting down all IPA services
Removing IPA client configuration
root        : ERROR    IPA cannot be re-installed without removing existing 389-ds instance(s)


Expected results:
It would be nice if IPA could uninstall while the other DS instances are around.

Comment 2 Rob Crittenden 2012-02-15 19:36:45 UTC

This will be fixed in next release. Upstream ticket was https://fedorahosted.org/freeipa/ticket/1735

Comment 3 Dmitri Pal 2012-02-22 14:47:31 UTC

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1735

Comment 4 Martin Kosek 2012-02-24 09:28:14 UTC

Upstream commit:
master: 8be0d84a599be48e837d498cec45d08cbccd3a03

Comment 6 Rob Crittenden 2012-03-14 14:38:04 UTC

I should add that this error wasn't that the uninstallation failed, it was warning that during uninstall it noticed that there are other instances around which would make re-installation not possible.

As I said, this was fixed upstream, but this is what the message was trying to say. remove-ds.pl does not fully remove instances (can't blame them, caution is good).

Comment 9 Martin Kosek 2012-04-24 11:48:27 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 10 Namita Soman 2012-05-10 18:36:11 UTC

Verified using ipa-server-2.2.0-12.el6.x86_64

Steps taken while verifying bug 751769 - which verifies this bug:
installed ipaserver
then ran setup-ds.pl, and followed prompts to set up a ds instance as specified
above
uninstalled ipa-server without uninstalling the ds instance - was successful.

reinstalled ipa server after ds-instance was uninstalled successfully

Comment 12 errata-xmlrpc 2012-06-20 13:18:46 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.

http://rhn.redhat.com/errata/RHBA-2012-0819.html