Bug 1443990 - [GANESHA] Volume start and stop having ganesha enable on it,turns off cache-invalidation on volume
Summary: [GANESHA] Volume start and stop having ganesha enable on it,turns off cache-i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Jiffin
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1417151 1445260
TreeView+ depends on / blocked
 
Reported: 2017-04-20 11:49 UTC by Manisha Saini
Modified: 2017-09-21 04:39 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.8.4-25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1445260 (view as bug list)
Environment:
Last Closed: 2017-09-21 04:39:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Description Manisha Saini 2017-04-20 11:49:41 UTC
Description of problem:
Volume having ganesha enable on it,after performing volume stop and start turns of features.cache-invalidation to off

Version-Release number of selected component (if applicable):
# rpm -qa | grep ganesha
glusterfs-ganesha-3.8.4-22.el7rhgs.x86_64
nfs-ganesha-2.4.4-2.el7.x86_64
nfs-ganesha-gluster-2.4.4-2.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Create 4 node ganesha cluster.
2.Create a volume.Enable ganesha on it
3.Do volume stop and start


Actual results:
features.cache-invalidation gets turned off while doing volume stop and start.
Volume is still exported after restart

Expected results:
features.cache-invalidation should not be turned off after doing volume start and stop

Additional info:

While ganesha is enabled on fresh volume
====

# gluster v info
 
Volume Name: ganesha1
Type: Distributed-Replicate
Volume ID: 793f86f4-7e0b-4b0d-a4e5-4fb8ab9b82c0
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dhcp47-132.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick2: dhcp47-141.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick3: dhcp47-144.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick4: dhcp47-139.lab.eng.blr.redhat.com:/gluster/brick1/1
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: on
transport.address-family: inet
nfs.disable: on
cluster.brick-multiplex: disable
nfs-ganesha: enable
cluster.enable-shared-storage: enable


======

After performing volume stop and start

# gluster v info
 
Volume Name: ganesha1
Type: Distributed-Replicate
Volume ID: 793f86f4-7e0b-4b0d-a4e5-4fb8ab9b82c0
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dhcp47-132.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick2: dhcp47-141.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick3: dhcp47-144.lab.eng.blr.redhat.com:/gluster/brick1/1
Brick4: dhcp47-139.lab.eng.blr.redhat.com:/gluster/brick1/1
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: off
transport.address-family: inet
nfs.disable: on
cluster.brick-multiplex: disable
nfs-ganesha: enable
cluster.enable-shared-storage: enable
 

# showmount -e localhost
Export list for localhost:
/ganesha1 (everyone)

Comment 5 Jiffin 2017-04-25 11:36:00 UTC
Patch posted upstream for review : https://review.gluster.org/17111

Comment 6 Jiffin 2017-05-03 06:05:17 UTC
Downstream patch link : https://code.engineering.redhat.com/gerrit/104974

Comment 8 Manisha Saini 2017-05-26 12:12:39 UTC
Verified this bug on glusterfs-ganesha-3.8.4-25.el7rhgs.x86_64

cache-invalidation option remain on while performing volume start and stop.Hence moving this bug to verified state

Comment 10 errata-xmlrpc 2017-09-21 04:39:40 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.

https://access.redhat.com/errata/RHBA-2017:2774


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