Bug 956761

Summary: RHQ Controll - storage node process is up always (even if it's stopped)
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: InstallerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jsanda, mfoley
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-25 15:54:21 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:    
Bug Blocks: 951619    
Attachments:
Description Flags
storage_node-status.png
none
storage_process.png
none
storage-exitValue.png none

Description Armine Hovsepyan 2013-04-25 14:51:35 UTC
Created attachment 739939 [details]
storage_node-status.png

Description of problem:
RHQ Controll - storage node process is up always (even if it's stopped)

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

How reproducible:
always

Steps to Reproduce:
1. run ./rhqctl.sh install --storage (both storage and agent are started)
2. run ./rhqcrl.sh stop  
3. killall -9 java
4. run ./rhqctl.sh status
  
Actual results:
After step2. shows error that storage cannot be stopped
Afters tep4. storage node is still visible as up - while there is no cassandra process is running

Expected results:
After step2. both agent and storage should be stopped

Additional info:
screenshots are attached

Comment 1 Armine Hovsepyan 2013-04-25 14:56:25 UTC
Created attachment 739951 [details]
storage_process.png

Comment 2 Armine Hovsepyan 2013-04-25 15:08:25 UTC
Created attachment 739953 [details]
storage-exitValue.png

Comment 3 John Sanda 2013-04-25 15:54:21 UTC
The status command simply checks for the pid files of each service. The killall -9 is an invalid step. If I forcibly kill a process with -9, the pid file won't get deleted. You will find this behavior with the server, agent, storage node, etc. I am going to close this bug since step 3 is not valid.