Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1355628 - Upgrade from 3.7.8 to 3.8.1 doesn't regenerate the volfiles
Summary: Upgrade from 3.7.8 to 3.8.1 doesn't regenerate the volfiles
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
Depends On: 1353470
Blocks: 1356426 1356439
TreeView+ depends on / blocked
Reported: 2016-07-12 06:24 UTC by Kotresh HR
Modified: 2017-03-08 09:31 UTC (History)
7 users (show)

Fixed In Version: v3.10.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1353470
: 1356426 (view as bug list)
Last Closed: 2017-03-08 09:31:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Comment 1 Kotresh HR 2016-07-12 06:26:47 UTC
Description of problem:

On CentOS6 base OS, post upgrade of gluster from 3.7.8 to 3.8.1, volfiles are not recreated. During upgrade, glusterd is brought up with "--xlator-option *.upgrade=on -N" parameters to ensure the volfiles are regenerated w.r.t latest bits but that fails as glusterd init () fails from glusterd_check_gsync_present () with a error log saying "0-glusterd: geo-replication module not working as desired".

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

How reproducible:

Additional info:

As a workaround, post 'yum update' following needs to be done.
1. grep -irns "geo-replication module not working as desired" /var/log/glusterfs/etc-glusterfs-glusterd.vol.log | wc -l

If the output is non-zero, then go to step 2

2. Check if glusterd instance is running or not by 'ps aux | grep glusterd', if it is, then stop the glusterd service.

3. glusterd --xlator-option *.upgrade=on -N

and then proceed ahead with the rest of the steps as per the upgrade section from installation guide.

Comment 2 Vijay Bellur 2016-07-12 06:31:07 UTC
REVIEW: (glusterd: Fix gsyncd upgrade issue) posted (#1) for review on master by Kotresh HR (

Comment 3 Vijay Bellur 2016-07-12 06:51:01 UTC
REVIEW: (glusterd: Fix gsyncd upgrade issue) posted (#2) for review on master by Kotresh HR (

Comment 4 Vijay Bellur 2016-07-13 15:02:58 UTC
COMMIT: committed in master by Atin Mukherjee ( 
commit 1b998788ece8c8b52657e8b9aae65d3279690c5b
Author: Kotresh HR <>
Date:   Tue Jul 12 00:39:31 2016 +0530

    glusterd: Fix gsyncd upgrade issue
        gluster upgrade is not generating new volfiles
    During upgrade, "glusterd --xlator-option *.upgrade=on -N"
    is run to generate new volfiles. It is run post 'glusterfs'
    rpm installation. The above command fails during upgrade
    if geo-replication is installed. This is because on
    glusterd start 'gsyncd' binary is called to configure
    geo-replication related stuff. Since 'glusterfs' rpm is
    installed prior to 'geo-rep' rpm, the 'gsyncd' binary
    used to glusterd upgrade command is of old version and
    hence it fails before generating new volfiles.
    Don't call geo-replication configure during upgrade/downgrade.
    Geo-replication configuration happens during start of glusterd
    after upgrade.
    Change-Id: Id58ea44ead9f69982f86fb68dc5b9ee3f6cd11a1
    BUG: 1355628
    Signed-off-by: Kotresh HR <>
    Reviewed-by: Atin Mukherjee <>
    Smoke: Gluster Build System <>
    CentOS-regression: Gluster Build System <>
    NetBSD-regression: NetBSD Build System <>

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