RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 731804 - [IPA] When upgrading ipa from 2.0.0-23 to 2.1.0-1 uninstall is leaving leftovers and reinstall fails.
Summary: [IPA] When upgrading ipa from 2.0.0-23 to 2.1.0-1 uninstall is leaving leftov...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-18 18:17 UTC by David Naori
Modified: 2015-01-04 23:50 UTC (History)
11 users (show)

Fixed In Version: ipa-2.1.1-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Upgrading IPA from 2.0.0-23 Consequence: The 389-ds configuration has been modified not to accept requests. Fix: Make the upgrade process more robust so it always restores the 389-ds configuration. When upgrading we disable the 389-ds listeners so modifications are not done during this window. An error was causing this process to abort and the 389-ds configuration was not being restored. Result: Upgrading IPA does not leave the system in an inconsistent state.
Clone Of:
Environment:
Last Closed: 2011-12-06 18:30:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1533 0 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-06 01:23:31 UTC

Description David Naori 2011-08-18 18:17:20 UTC 
Description of problem:
When upgrading ipa from 2.0.0-23 to 2.1.0-1 uninstall command is leaving leftovers (/var/lib/ipa/sysrestore/sysrestore.state) and reinstall fails.

[root@camel-prod ipa]# ipa-server-install --uninstall

This is a NON REVERSIBLE operation and will delete all data and configuration!

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@camel-prod ipa]# ipa-server-install 

The log file for this installation can be found in /var/log/ipaserver-install.log
IPA server is already configured on this system.
If you want to reinstall the IPA server please uninstall it first.

[root@camel-prod ipa]# cat /var/log/ipaserver-install.log 
2011-08-18 21:09:48,483 DEBUG Loading StateFile from '/var/lib/ipa/sysrestore/sysrestore.state'
2011-08-18 21:09:48,484 DEBUG Loading Index file from '/var/lib/ipa/sysrestore/sysrestore.index'

[root@camel-prod ipa]# cat /var/lib/ipa/sysrestore/sysrestore.state
[dirsrv]
nsslapd-ldapiautobind = on
nsslapd-port = 389
nsslapd-security = on

(/var/lib/ipa/sysrestore/sysrestore.index No such file or directory)


Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Rob Crittenden 2011-08-18 18:24:14 UTC 
https://fedorahosted.org/freeipa/ticket/1667
Comment 2 Rob Crittenden 2011-08-24 13:13:15 UTC 
Do you remember the sequence of events with this instance?

Did you install 2.0, upgrade to 2.1, uninstall and try to re-install?

Or did you start with 2.0, upgrade to another release of 2.0, then uninstall the instance, update to 2.1 and try to re-install??
Comment 3 David Naori 2011-08-24 13:24:37 UTC 
(In reply to comment #2)
> Did you install 2.0, upgrade to 2.1, uninstall and try to re-install?
Correct.
Comment 4 Rob Crittenden 2011-08-26 18:05:06 UTC 
Cleaning up upgrade state is fixed upstream in:

master: e4b62d05294c6d00fddd1ad574085ddba1b887ee

ipa-2-1: c3ee9b32087c2f5778d70d8ada4508db5a56f6bf
Comment 6 Rob Crittenden 2011-11-01 13:35:13 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:
Cause: Upgrading IPA from 2.0.0-23
Consequence: The 389-ds configuration has been modified not to accept requests.
Fix: Make the upgrade process more robust so it always restores the 389-ds configuration. When upgrading we disable the 389-ds listeners so modifications are not done during this window. An error was causing this process to abort and the 389-ds configuration was not being restored.
Result: Upgrading IPA does not leave the system in an inconsistent state.
Comment 7 Namita Soman 2011-11-08 02:45:43 UTC 
testing
Comment 8 Namita Soman 2011-11-08 04:02:12 UTC 
Started with ipa-server.x86_64 0:2.0.0-23.el6. Installed. kinited as admin, added a user. 
Then did a yum update ipa-server to get ipa-server-2.1.3-8.el6.x86_64. 
restarted service - ipactl restart
kinit'd as admin and also as the user added previously
then uninstalled
reinstalled
added a new user

verified installing 2.0, upgrading to 2.1.3, uninstalling and re-installing
Comment 9 errata-xmlrpc 2011-12-06 18:30:00 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/RHSA-2011-1533.html
Note You need to log in before you can comment on or make changes to this bug.