[Bugs] [Bug 1356439] Upgrade from 3.7.8 to 3.8.1 doesn't regenerate the volfiles
bugzilla at redhat.com
bugzilla at redhat.com
Fri Jul 15 16:47:48 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1356439
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14916 committed in release-3.8 by Atin
Mukherjee (amukherj at redhat.com)
------
commit ddcfe83b06b6498710c2d9d36027a8ad305b686e
Author: Kotresh HR <khiremat at redhat.com>
Date: Tue Jul 12 00:39:31 2016 +0530
glusterd: Fix gsyncd upgrade issue
Backport of http://review.gluster.org/14898/
Problem:
gluster upgrade is not generating new volfiles
Cause:
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.
Solution:
Don't call geo-replication configure during upgrade/downgrade.
Geo-replication configuration happens during start of glusterd
after upgrade.
Change-Id: Id58ea44ead9f69982f86fb68dc5b9ee3f6cd11a1
BUG: 1356439
Signed-off-by: Kotresh HR <khiremat at redhat.com>
Reviewed-on: http://review.gluster.org/14898
(cherry picked from commit 1b998788ece8c8b52657e8b9aae65d3279690c5b)
Reviewed-on: http://review.gluster.org/14916
Smoke: Gluster Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=UbTNaNs2Vo&a=cc_unsubscribe
More information about the Bugs
mailing list