Bug 1007042

Summary:	packstack should support uninstall or rollback or "transactions"
Product:	[Fedora] Fedora	Reporter:	John Dennis <jdennis>
Component:	openstack-packstack	Assignee:	Martin Magr <mmagr>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	derekh, itamar, Jan.van.Eldik, mmagr, p, rharwood, sandro
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 17:09:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description John Dennis 2013-09-11 19:11:28 UTC

During my testing at various points packstack failed. This seems leaves the system in some weird unknown state that's hard to recover from. Trying to run packstack again with the prior answer file did not produce a successful installation. 

Now what do you do?

I asked if there was a packstack uninstall command and I got pointed to this:

http://openstack.redhat.com/Uninstalling_RDO

Ugh!

First of all I'm not sure which of these methods I should be using and even if I did I don't want to have to create my own script to do it.

I should be able to run "packstack --uninstall" and have it return my system to it's prior state before I ran packstack. FWIW we can do this in IPA and our installations are just as complex (installing many software packages and configuring them, running services, etc.)

I have no proof of this, but it seems as if running packstack again with the previous answer file because it doesn't seem to restart in a clean state. For instance I had to control-c out of packstack and I'm guess this happened in-between some step. Either it should have the concept of a transaction or do a better job of recording exactly what the last successful operation was.

FWIW in IPA we don't attempt to restart installation, if installation fails you do a complete uninstall which reverts everything to a virgin state and then you install again from scratch.

Comment 1 Fedora Admin XMLRPC Client 2013-10-14 09:51:39 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2013-10-14 09:52:19 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-01-09 19:48:30 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 17:09:14 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.