[Bugs] [Bug 1737676] New: Upgrading a Gluster node fails when user edited glusterd.vol file exists

bugzilla at redhat.com bugzilla at redhat.com
Tue Aug 6 03:17:43 UTC 2019


            Bug ID: 1737676
           Summary: Upgrading a Gluster node fails when user edited
                    glusterd.vol file exists
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: amukherj at redhat.com, bmekala at redhat.com,
                    bugs at gluster.org, rhs-bugs at redhat.com,
                    rtalur at redhat.com, sankarshan at redhat.com,
                    storage-qa-internal at redhat.com, vbellur at redhat.com
            Blocks: 1734534
  Target Milestone: ---
    Classification: Community

+++ This bug was initially created as a clone of Bug #1734534 +++

Description of problem:
When a user had edited the glusterd.vol file in /etc/glusterfs and updates the
glusterfs packages, bricks cannot contact glusterd.

Version-Release number of selected component (if applicable):
glusterfs-6 and above (including mainline)

How reproducible:

Steps to Reproduce:
1. install glusterfs-5 or lower
2. create and start a volume
3. edit glusterd.vol and  modify options like base port / max port
4. yum update gluster packages to glusterfs-6
5. restart volumes

Actual result:

bricks can't talk to glusterd

Expected result:

bricks should be able to talk to glusterd on 24007.

--- Additional comment from Raghavendra Talur on 2019-08-05 14:33:01 UTC ---

I think the change happened in c96778b354ea82943442aab158adbb854ca43a52 commit
upstream and I propose that we fix this problem by keeping the default in code
for glusterd and letting glusterd.vol override ride instead of having the value
only in glusterd.vol.

Referenced Bugs:

[Bug 1734534] Upgrading a RHGS node fails when user edited glusterd.vol file
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list