Bug 922757

Summary: [RHSC] -Services tab in cluster - While checking the status of a volume the values which shows in CLI are different from GUI.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Kanagaraj <kmayilsa>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: bhubbard, rhs-bugs, sabose, sankarshan
Target Milestone: ---   
Target Release: RHGS 2.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qa10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:26:07 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
Engine ,vdsm and glusterfs logs. none

Description RamaKasturi 2013-03-18 12:49:40 UTC 
Description of problem:While checking the status of a volume the values which shows in CLI are different from GUI.


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


How reproducible:


Steps to Reproduce:
1. Login to RHSC 
2. Create replicate volume and start it.
3. Click on the cluster under which the volume was created . 
4. There is a subtab called Services on the clusters tab. Click on that tab.
5. You can see two process alled SHD and NFS with their port no and process ID.
6. For SHD service the port no is "0".
7. Go to any one of the rhs nodes and type the command "gluster volume status <volname>"
8.The output it returns contains the port no and Process ID. it gives SHD port no as N/A.
  
Actual results:

IN CLI port no for SHD is "N/A" and in UI it is  "0".  

Expected results:

On both UI and CLI port no for SHD should be N/A and not 0.

Additional info:
Comment 1 RamaKasturi 2013-03-18 12:53:08 UTC 
Created attachment 711945 [details]
Engine ,vdsm and glusterfs logs.
Comment 3 Scott Haines 2013-09-23 22:26:07 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