Bug 1253598 - Installation fails when SPACE character occurs in installation path
Installation fails when SPACE character occurs in installation path
Status: VERIFIED
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Installer (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: ER1
: 6.2.0
Assigned To: Thomas Hauser
Dominik Hanak
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-14 04:25 EDT by Dominik Hanak
Modified: 2015-08-27 02:37 EDT (History)
1 user (show)

See Also:
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: ---


Attachments (Terms of Use)
InstallationLog (104.92 KB, text/plain)
2015-08-14 04:25 EDT, Dominik Hanak
no flags Details

  None (edit)
Description Dominik Hanak 2015-08-14 04:25:47 EDT
Created attachment 1062932 [details]
InstallationLog

Description of problem:
Installation fails when there is space in installation path.

Version-Release number of selected component (if applicable):
6.2.0.DR1

How reproducible:
Install bxms with space in installation path.

Steps to Reproduce:
1. Unzip EAP into path with space character (path to eap contains space (/.../eap[space]eap...)
2. Install using this path

Actual results:
Installation fails.

Expected results:
Installation finishes successfully

Additional info:
Happens because CLI uses installation path as argument of command and when space character is in it, it will fail. It is because the command expects only one argument but with space in path, it thinks it is getting two.

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