Bug 1090049

Summary: Cannot install custom password vault outside EAP directory
Product: [Retired] JBoss BRMS Platform 6 Reporter: Tomas Livora <tlivora>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Livora <tlivora>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: aabulawi, apodhrad, kverlaen, rrajasek
Target Milestone: ER3   
Target Release: 6.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:53:49 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:
Embargoed:
Attachments:
Description Flags
Installation Log none

Description Tomas Livora 2014-04-22 13:04:59 UTC 
Created attachment 888478 [details]
Installation Log

Description of problem:
If you want to create custom password vault outside jboss-eap-6.1 directory the installation process will fail. This prevents users from creating custom password vault when installing both BRMS and EAP at once as the EAP folder does not exist at the moment when you select keystore location. Also the default keystore location in BRMS installer is outside that directory.

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

Steps to Reproduce:
1. Run the installer and proceed to the page with title 'Configure runtime environment'.
2. Select 'Perform advanced configuration' and check 'Install password vault'.
3. On the next screen fill in password fields, leave default values in the other fields.
4. Try to finish the installation.

Actual results:
The installation process will fail in the last step when EAP is run.

Expected results:
The installation process should finish successfully.

Additional info:
This issue only affects BRMS installer. BPMS installer allows users to create password vault wherever they want (only limited by bug 1090036).
Comment 1 Thomas Hauser 2014-04-22 22:32:32 UTC 
The fix for 1090036 fixes this issue also.
Comment 2 Tomas Livora 2014-04-29 14:14:46 UTC 
The fix for bug 1090036 did not get into ER2. However, this BZ is slightly different and depends on it only partially. This BZ is primarily not about the default keystore location but rather about not being able to create keystore file outside jboss-eap-6.1 directory. I should correct the description above, it does not work in BPMS installer either.
Comment 3 Thomas Hauser 2014-04-30 16:27:42 UTC 
The reason this and 1090036 are not present in the ER2 build is because the builder.cfg posted here: http://dev138.mw.lab.eng.bos.redhat.com/candidate/brms-6.0.2-ER2/builder.cfg does not contain the change from commit ab272289269535497e8a38d4cceb2360f472afdb some how. Once the installer is built with the right (newest) version of installer-commons, the fixes for this and 1090036 will be present.
Comment 4 Andrej Podhradsky 2014-05-30 17:10:21 UTC 
Verified with BRMS Installer 6.0.2.ER3