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
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):
Steps to Reproduce:
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??
(In reply to comment #2)
> Did you install 2.0, upgrade to 2.1, uninstall and try to re-install?
Cleaning up upgrade state is fixed upstream in:
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.
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.
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
added a new user
verified installing 2.0, upgrading to 2.1.3, uninstalling and re-installing
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.