Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1074878

Summary: Cannot install BRMS into existing FSW
Product: [Retired] JBoss BRMS Platform 6 Reporter: Andrej Podhradsky <apodhrad>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED DEFERRED QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.1CC: kverlaen, mbaluch, rrajasek, tlivora
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: 2014-06-13 19:20:44 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
Screenshot none

Description Andrej Podhradsky 2014-03-11 07:46:14 UTC 
Description of problem:
Cannot install BRMS into an existing FSW due to invalid password vault. The instaler detects that password vault was configured (during FSW installation). But when I type the correct password vauld I'm still getting the following warning

The given credentials were incorect ... (see the attchament)

When I press OK then the installation fails :(

Version-Release number of selected component (if applicable):
6.0.1.ER2

How reproducible:
always

Steps to Reproduce:
1. Install FSW 6.0.0.CR4 (fswAdmin123$,saml.storepass=saml123$,vault.keystorepwd=vault123$)
2. Try to install BRMS 6.0.1.ER2
3. When the installer asks for password vault, type vault123$

Actual results:


Expected results:


Additional info:
Comment 1 Andrej Podhradsky 2014-03-11 07:46:52 UTC 
Created attachment 872992 [details]
Screenshot
Comment 2 Thomas Hauser 2014-03-11 14:30:00 UTC 
I was under the impression that layering isn't going to be supported until 6.1.0 of FSW / DV / SRAMP etc. 

The reason that the current build of the BRMS installer reports that the credentials are incorrect are because the default FSW vault uses a server property as its location (and we cannot query this without running the server, which hasn't happened at this point), so the code that tries to open the keystore is using the literal "${jboss.server.config.dir}" as the keystore location and failing, obviously. The newer code can deal with this, but this code was not put into BRMS 6.0.1 (because of the aforementioned reason).

Without changes to the BRMS assembly (the *.cli) FSW + BRMS will have clashing commands and installation will fail anyways.
Comment 3 Thomas Hauser 2014-06-13 19:11:31 UTC 
Is this going to be supported for 6.1.0?