Bug 1254467

Summary: gstatus: gtatus show wrong protocols information which are currently being used
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Anil Shah <ashah>
Component: gstatusAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED NOTABUG QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: high    
Version: rhgs-3.1CC: asrivast, byarlaga, surs, vagarwal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-27 12:07:50 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: 1251815    

Description Anil Shah 2015-08-18 08:21:30 UTC 
Description of problem:

when you run gstatus  command, its shows all the protocols (NFS,FUSE and SAMBA) being turned on , irrespective of it is being used on not.

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

[root@localhost ~]# gstatus --version
gstatus 0.64

[root@localhost ~]# rpm -qa | grep glusterfs
glusterfs-api-3.7.1-11.el7rhgs.x86_64
glusterfs-cli-3.7.1-11.el7rhgs.x86_64
glusterfs-libs-3.7.1-11.el7rhgs.x86_64
glusterfs-client-xlators-3.7.1-11.el7rhgs.x86_64
glusterfs-server-3.7.1-11.el7rhgs.x86_64
glusterfs-rdma-3.7.1-11.el7rhgs.x86_64
glusterfs-3.7.1-11.el7rhgs.x86_64
glusterfs-fuse-3.7.1-11.el7rhgs.x86_64
glusterfs-geo-replication-3.7.1-11.el7rhgs.x86_64


How reproducible:

100%

Steps to Reproduce:
1. Create 6X2 distribute replicate volume
2. Mount volume as FUSE mount on client 
3. check gstatus. e.g gstatus -a
  

Actual results:
it show all the protocols (NFS.FUSE and SAMBA) turned  
Protocols: glusterfs:on  NFS:on  SMB:on

Expected results:

gstatus should show which ever protocol is on.

Additional info:
Comment 3 Sachidananda Urs 2015-08-27 12:07:50 UTC 
This is a expected behavior.

It shows all the protocols that are enabled by default. If they are explicitly
set off like `user.cifs disable', `nfs.disable on' ...

These are picked up by looking at the config files, killing a process explicityly
doesn't affect this.