diff options
| author | Atin Mukherjee <amukherj@redhat.com> | 2015-07-30 09:40:24 +0530 |
|---|---|---|
| committer | Kaushal M <kaushal@redhat.com> | 2015-08-03 21:25:48 -0700 |
| commit | b467b97e4c4546b7f870a3ac624d56c62bfa5cf9 (patch) | |
| tree | 1daa4217b0f8685d17f1209b3310040b0db8bd47 /cli/src/cli-cmd-peer.c | |
| parent | b646aa00bb2558fe82f80ca8a43f187611d288c9 (diff) | |
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@redhat.com>
Reviewed-on: http://review.gluster.org/11798
Reviewed-by: Avra Sengupta <asengupt@redhat.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Kaushal M <kaushal@redhat.com>
Diffstat (limited to 'cli/src/cli-cmd-peer.c')
0 files changed, 0 insertions, 0 deletions