Bug 1248298
Summary: | [upgrade] After upgrade from 3.5 to 3.6 onwards version, bumping up op-version failed | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Atin Mukherjee <amukherj> | |
Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, gluster-bugs, nlevinki, rhs-bugs, sasundar, vbellur | |
Target Milestone: | --- | Keywords: | Reopened, Triaged | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | glusterd | |||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1247947 | |||
: | 1249921 1250836 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:27:16 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1249921, 1250836 |
Description
Atin Mukherjee
2015-07-30 04:17:28 UTC
REVIEW: http://review.gluster.org/11798 (glusterd: fix op-version bump up flow) posted (#1) for review on master by Atin Mukherjee (amukherj) COMMIT: http://review.gluster.org/11798 committed in master by Kaushal M (kaushal) ------ commit b467b97e4c4546b7f870a3ac624d56c62bfa5cf9 Author: Atin Mukherjee <amukherj> Date: Thu Jul 30 09:40:24 2015 +0530 glusterd: fix op-version bump up flow If a cluster is upgraded from 3.5 to latest version, gluster volume set all cluster.op-version <VERSION> will throw an error message back to the user saying unlocking failed. This is because of trying to release a volume wise lock in unlock phase as the lock was taken cluster wide. The problem surfaced because the op-version is updated in commit phase and unlocking works in the v3 framework where it should have used cluster unlock. Fix is to decide which lock/unlock is to be followed before invoking lock phase Change-Id: Iefb271a058431fe336a493c24d240ed833f279c5 BUG: 1248298 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/11798 Reviewed-by: Avra Sengupta <asengupt> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Anand Nekkunti <anekkunt> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |