Bug 1009655 - Error reported after apparently successful ER3 install (not reproducible at will)
Error reported after apparently successful ER3 install (not reproducible at w...
Status: CLOSED NOTABUG
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer (Show other bugs)
6.0.0
Unspecified Unspecified
unspecified Severity urgent
: ---
: ---
Assigned To: Thomas Hauser
Len DiMaggio
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-18 15:38 EDT by Len DiMaggio
Modified: 2013-09-25 08:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-18 21:53:24 EDT
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)
Screenshot (1013.03 KB, image/png)
2013-09-18 15:45 EDT, Len DiMaggio
no flags Details
Screenshot (1014.28 KB, image/png)
2013-09-18 21:52 EDT, Len DiMaggio
no flags Details

  None (edit)
Description Len DiMaggio 2013-09-18 15:38:21 EDT
Description of problem:

After what appeared to be a clean install, the error shown in the attached screenshot was seen at the conclusion of the install.


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

http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0-ER3/jboss-eap-6.1.0.soa.ci-installer.jar

RHEL 6.5

java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)


How reproducible:


Steps to Reproduce:
1. Installed from the installer jar - accepted all defaults
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Len DiMaggio 2013-09-18 15:45:01 EDT
Created attachment 799560 [details]
Screenshot
Comment 3 Thomas Hauser 2013-09-18 16:53:04 EDT
Please try to paste the content of the ProcessPanel next time please. This kind of ending screen indicates that some critical job has failed, whether that is a .cli script execution or a server launch. It could also be the failure of the s-ramp ontology upload. Please gather this information and paste those contents to facilitate debugging this issue.
Comment 4 Len DiMaggio 2013-09-18 21:52:17 EDT
Closing as not reproducible - it's working now. Will try again (and again)...
Comment 5 Len DiMaggio 2013-09-18 21:52:52 EDT
Created attachment 799663 [details]
Screenshot

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