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

Bug 1113492

Summary: Installation fails when using specific keystore password
Product: [Retired] JBoss BPMS Platform 6 Reporter: Tomas Livora <tlivora>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED CANTFIX QA Contact: Tomas Livora <tlivora>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.2CC: kverlaen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1125004 (view as bug list) Environment:
Last Closed: 2014-10-15 15:59:38 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:
Bug Depends On: 1125004    
Bug Blocks:    
Attachments:
Description Flags
Installation Log none

Description Tomas Livora 2014-06-26 09:38:28 UTC
Created attachment 912387 [details]
Installation Log

Description of problem:
Installation sometimes fails if a specific vault keystore password is entered.

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

Steps to Reproduce:
1. Run the installer and proceed to the page 'Configure password vault'.
2. Type "vault1" into both fields.
3. Try to complete the installation.

Actual results:
The installation process fails with IllegalBlockSizeException. The details can be found in the attached installation log.

Expected results:
No exception and successfully finished installation.

Additional info:
If "vaultt" or "vault22" is used as a keystore password, the installation finishes without any problems.

Comment 3 Thomas Hauser 2014-07-31 20:06:37 UTC
Sorry, this issue depends on 1125004 (1125004 blocks it.)

Comment 5 Thomas Hauser 2014-10-15 15:59:38 UTC
Looks like this is fixed in EAP 6.4.0.DR2 and beyond, so it looks like we cannot fix this problem in this release, unfortunately.