Bug 1009519 - storage re-installation fails if 1st server installation failed
Summary: storage re-installation fails if 1st server installation failed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Solaris
unspecified
high
Target Milestone: ER03
: RHQ 4.10
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: jon32-Beta-Blockers-1006862
TreeView+ depends on / blocked
 
Reported: 2013-09-18 15:01 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-23 12:32:21 UTC
Embargoed:


Attachments (Terms of Use)
storage-commitlog-exists.log (1.53 KB, text/x-log)
2013-09-19 09:52 UTC, Armine Hovsepyan
no flags Details

Description Armine Hovsepyan 2013-09-18 15:01:58 UTC
Description of problem:
storage re-installation fails if 1st server installation failed

Version-Release number of selected component (if applicable):
rhq 4.9 released version

How reproducible:
always

Steps to Reproduce:
1. change rhq-server.property make a typo for rhq.server.database.connection-url replacing it with dhq.server.database.connection-url
2. run rhqctl install
3. change property and fix the typo
4. re-run rhqctl install

Actual results:
After step4. storage directory cannot be installed cause of existing storage data -> http://pastebin.test.redhat.com/164706

Expected results:
After step4. old directory is removed and new one is created 
corresponding changed are added into documentation -> https://docs.jboss.org/author/display/RHQ/RHQ+Control+Script

Additional info:
environment: SunOS solaris11 5.11 11.1 i86pc i386 i86pc

Comment 1 Armine Hovsepyan 2013-09-19 09:52:04 UTC
Created attachment 799809 [details]
storage-commitlog-exists.log

log copy-pasted into separate file in case pastebin is not accessible

Comment 2 John Mazzitelli 2013-09-26 12:06:58 UTC
this is being addressed - and is currently fixed in master.

Comment 3 John Mazzitelli 2013-09-26 12:13:58 UTC
the main commit to master is b130f6a4194d944fae8fc582fca8f561c37922f9 but there were other commits later than refined the "install undo" feature. But this should be fixed in master now. I'm still testing this feature - it may need to be refined.

Comment 4 John Mazzitelli 2013-10-04 21:05:10 UTC
in addition to git commit b130f6a4194d944fae8fc582fca8f561c37922f9 these are also part of the fix:

d2410ab75b1274867bb9b7f378219974519e6426
52bd8ca8f3b5e16e4f79e011a906406410579844
d7d3a9af3e1099fe590d0213859ffcfa501de294
2361b825acc4f1da3a7ff5617638c8b2b98e42df
f36fa3e0f783f179cb1409c22ab67c1c961578e1
d1dc34f4c2fd223735ae2e1b2e242732611d03fc
87740ae36b3d268b125f390ae7072e924051b601
093b388081bafff554293bd24ed52d1157aed376

Comment 5 Armine Hovsepyan 2013-12-06 14:20:40 UTC
marking as verified (verified in jon 3.2.x branch)

Comment 6 Heiko W. Rupp 2014-04-23 12:32:21 UTC
Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.


Note You need to log in before you can comment on or make changes to this bug.