Bug 956892 - RHQ Control - install fails for IBM java environment
Summary: RHQ Control - install fails for IBM java environment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Installer
Version: JON 3.2
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
: JON 3.2.0
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 951619
TreeView+ depends on / blocked
 
Reported: 2013-04-25 22:51 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
install_storage_ibm.png (315.22 KB, image/png)
2013-04-25 22:51 UTC, Armine Hovsepyan
no flags Details
rhq_control_install_ibm.png (319.35 KB, image/png)
2013-04-25 23:28 UTC, Armine Hovsepyan
no flags Details
rhq_control_install_storage_ibm.png (327.75 KB, image/png)
2013-04-25 23:34 UTC, Armine Hovsepyan
no flags Details
rhq_control_install_ibm_top.png (265.96 KB, image/png)
2013-04-26 22:56 UTC, Armine Hovsepyan
no flags Details
rhq_control_install_sstorage_ibm_top.png (272.66 KB, image/png)
2013-04-26 22:56 UTC, Armine Hovsepyan
no flags Details
rhqctl_install_agent_ibm.png (305.54 KB, image/png)
2013-04-26 23:00 UTC, Armine Hovsepyan
no flags Details
rhq_ctl_install_agent_ibm.png (291.53 KB, image/png)
2013-04-26 23:04 UTC, Armine Hovsepyan
no flags Details

Description Armine Hovsepyan 2013-04-25 22:51:53 UTC
Created attachment 740091 [details]
install_storage_ibm.png

Description of problem:
RHQ Control - install --storage fails for IBM java environment  after showing a message storage is installed and never reaches the agent installation.

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

How reproducible:
3 out of 3

Steps to Reproduce:
1. in a clear ibm java environment run ./rhqctl.sh install --storage
2.
3.
  
Actual results:
Error (screenshot attached) is shown after a message that storage is installed

Expected results:
no error is visible. storage and agent are installed and running on environment

Additional info:

Comment 1 Armine Hovsepyan 2013-04-25 23:27:44 UTC
for some unknown reason, now the storage is being installed and server is throwing an exception. please get the screenshot attached.

Comment 2 Armine Hovsepyan 2013-04-25 23:28:30 UTC
Created attachment 740111 [details]
rhq_control_install_ibm.png

Comment 4 Armine Hovsepyan 2013-04-25 23:34:21 UTC
Created attachment 740122 [details]
rhq_control_install_storage_ibm.png

Comment 5 Armine Hovsepyan 2013-04-26 22:56:15 UTC
Created attachment 740649 [details]
rhq_control_install_ibm_top.png

Comment 6 Armine Hovsepyan 2013-04-26 22:56:49 UTC
Created attachment 740650 [details]
rhq_control_install_sstorage_ibm_top.png

Comment 7 Armine Hovsepyan 2013-04-26 23:00:10 UTC
Created attachment 740652 [details]
rhqctl_install_agent_ibm.png

Comment 8 Armine Hovsepyan 2013-04-26 23:04:06 UTC
Created attachment 740653 [details]
rhq_ctl_install_agent_ibm.png

Comment 9 Armine Hovsepyan 2013-04-26 23:05:12 UTC
From last 2 screenshots attached - it seems that issue is not with cassandra but with agent installation.

Comment 10 Jay Shaughnessy 2013-04-30 19:08:30 UTC
The issue here was not the JDK/JRE but rather the PATH as set up in .bashrc in the test environment.

  export PATH=$JAVA_HOME:$PATH

needed to be changed to:

  export PATH=$JAVA_HOME/bin:$PATH


The root cause was that Java could not be found or launched when we tried to install the agent.

I believe this can be closed as 'not a bug'.

Comment 11 John Sanda 2013-05-01 00:02:04 UTC
I will move this to ON_QA. Armine, can you please make sure that your environment variables are set correctly and retest.

Comment 12 Armine Hovsepyan 2013-05-02 20:39:49 UTC
There is an issue with Cassandra installation/startup in ibm x32 arch environment (10.16.23.158) #956878

marking this bug as verified since the problem is not connected to rhq control script.

thank you.


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