Bug 1016885

Summary: log what is happening when undoing things after a failed install/upgrade
Product: [JBoss] JBoss Operations Network Reporter: John Mazzitelli <mazz>
Component: InstallerAssignee: John Mazzitelli <mazz>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: JON 3.2CC: ahovsepy
Target Milestone: ER04   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
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:    
Bug Blocks: 1012435    
Attachments:
Description Flags
install_db-error
none
storage-node-installed-error
none
upgrade-storageDataDir-permission-error none

Description John Mazzitelli 2013-10-08 20:58:35 UTC
When an install or upgrade failed, we should log messages as the undo-tasks are executed so people can see what the installer is doing when it backs out any changes and removes remnants from the failed install/upgrade.

Comment 1 John Mazzitelli 2013-10-08 20:59:38 UTC
this should go in JON 3.2 since it will help debug install issues

Comment 2 John Mazzitelli 2013-10-08 21:15:48 UTC
git commit to master: 79402bc

Comment 3 John Mazzitelli 2013-10-18 15:26:47 UTC
fyi: this is going to be a hard one to cherry pick I think - because one of the classes looks to be drastically changed.

Comment 4 Simeon Pinder 2013-10-24 04:09:47 UTC
Moving to ON_QA for testing in the next build.

Comment 5 Armine Hovsepyan 2013-11-11 12:45:18 UTC
Created attachment 822385 [details]
install_db-error

Comment 6 Armine Hovsepyan 2013-11-11 12:45:43 UTC
Created attachment 822386 [details]
storage-node-installed-error

Comment 7 Armine Hovsepyan 2013-11-11 12:46:25 UTC
Created attachment 822387 [details]
upgrade-storageDataDir-permission-error

Comment 8 Armine Hovsepyan 2013-11-11 12:48:26 UTC
verified with the following cases:
* installing jon when no db exists
* upgrading jon with no access to storage root dir
* upgrading jon having already installed/upgraded same version

screen-shots attached

please assign back to me if risky scenario is missing