[Bugs] [Bug 1250836] [upgrade] After upgrade from 3.5 to 3.6 onwards version, bumping up op-version failed

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1250836



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11849 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit fb601c73d366376711f5f164924a7655982e887f
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Aug 6 12:18:10 2015 +0530

    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 at redhat.com>
    Reviewed-on: http://review.gluster.org/11849
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra 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=UZEKwGOMrc&a=cc_unsubscribe