Bug 1310089 - glusterfs-nfs gets started on all the nodes after entire cluster upgrade to 3.1.2
Summary: glusterfs-nfs gets started on all the nodes after entire cluster upgrade to 3...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nfs-ganesha
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jiffin
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 12:23 UTC by Shashank Raj
Modified: 2017-03-25 14:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-25 14:23:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shashank Raj 2016-02-19 12:23:37 UTC 
Description of problem:
glusterfs-nfs gets started on all the nodes after entire cluster upgrade to 3.1.2

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

How reproducible:
once

Steps to Reproduce:
1. Create a 4 node cluster and install 3.1 rhgs.
2. Upgrade all the nodes of the cluster together by following the nfs-ganesha upgrade document.
3. Once the nodes are updated and we start glusterd on all the nodes, glusterfs-nfs gets started on all the nodes.

Actual results:


Expected results:
glusterfs-nfs should not start after upgrade to 3.1.2


Additional info:
Comment 3 Shashank Raj 2016-02-24 10:14:10 UTC 
I performed an upgrade of nfs-ganesha from 3.1.1 to 3.1.2, and after upgrade i didn't observe this issue.

nfs.disable values were same both before and after the upgrade.

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