Bug 1458672

Summary: DV 6.4 installation on windows fails during the EAP patch step
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Andrej Smigala <asmigala>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Stastny <jstastny>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.4.0CC: drieden, gjospin, vhalbert
Target Milestone: DR4   
Target Release: 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-13 17:36:59 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:
Bug Depends On: 1408961    
Bug Blocks:    

Description Andrej Smigala 2017-06-05 07:48:28 UTC
When running the DR3 installer on windows, it fails during the step which patches EAP 6.4.9 to 6.4.15

This is logged in the console:

IzPack variable state written to C:\Users\Administrator\DV-6.4.0-DR3\installation\InstallationLog.txt
Running command:[C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.9-patch.zip"]
    "outcome" : "success",
    "result" : {}
Exit code: 0
Command success: [C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.9-patch.zip"] completed successfully.
Running command:[C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.15-patch.zip"]
    "outcome" : "success",
    "result" : {}
patching exception
Exit code: 1
Command failure: [C:\Users\Administrator\DV-6.4.0-DR3\bin\jboss-cli.bat, "patch apply C:\Users\Administrator\DV-6.4.0-DR3\jboss-eap-6.4.15-patch.zip"] failed with exit code: 1
Running on-fail server check.
Server startup not recorded. No need to shut it down.
Shutting server down.
Trying to connect to Management Interface...(1/5).
Trying to connect to Management Interface...(2/5).
Trying to connect to Management Interface...(3/5).
Trying to connect to Management Interface...(4/5).
Trying to connect to Management Interface...(5/5).
Failed to connect to Management Interface after 5 attempts.
{"outcome" => "failed","failure-description" => "No ModelControllerClient was available to execute the request.","command" => ":shutdown"}
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\standalone\log\server.log doesn't exist.
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\domain\log\host-controller.log doesn't exist.
The configured source file: C:\Users\Administrator\DV-6.4.0-DR3\domain\log\process-controller.log doesn't exist.