Bug 973608

Summary: [RHS-C] Service status is showing as "RUNNING" instead of "Up"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: dtsang, knarra, mmahoney, pprakash, rhs-bugs, sabose, sdharane, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: bb4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:25:48 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:
Attachments:
Description Flags
screenshot of error none

Description Prasanth 2013-06-12 10:35:29 UTC
Created attachment 760086 [details]
screenshot of error

Description of problem:

Service status is showing as "RUNNING" instead of "Up". As per http://www.ovirt.org/Features/GlusterVolumeAdvancedDetails, it should be Up/Down


Version-Release number of selected component (if applicable):  Red Hat Storage Console Version: 2.1.0-0.bb3.el6rhs 


How reproducible: Always


Steps to Reproduce:
1. Create a cluster and add a couple of servers
2. Create a distribute and replicate volume and start it
3. Click on Clusters >> Services tab, and see the status of NFS and SHD


Actual results: Status is see as "RUNNING"


Expected results: Status should be Up/Down as mentioned in http://www.ovirt.org/Features/GlusterVolumeAdvancedDetails


Additional info: Screenshots attached

Comment 2 Prasanth 2013-06-21 09:51:47 UTC
Verified as fixed in bb4. 

The status is now showing as Up.

Comment 3 Scott Haines 2013-09-23 22:25:48 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html