diff options
| author | Atin Mukherjee <amukherj@redhat.com> | 2015-08-06 12:18:10 +0530 |
|---|---|---|
| committer | Raghavendra Bhat <raghavendra@redhat.com> | 2015-08-14 01:49:23 -0700 |
| commit | fb601c73d366376711f5f164924a7655982e887f (patch) | |
| tree | ac1f295e044e422bbb2eac4a1426b73bc78d1200 /cli/src/cli-xml-output.c | |
| parent | a28d161733e670d264999c6f486915bf738a7bfd (diff) | |
glusterd: fix op-version bump up flow
Backport of http://review.gluster.org/#/c/11798/
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: I6a82251d88cfc7af36c7deec511c634a09e55004
BUG: 1250836
Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-on: http://review.gluster.org/11849
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'cli/src/cli-xml-output.c')
0 files changed, 0 insertions, 0 deletions