[Bugs] [Bug 1248298] [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=1248298



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11798 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit b467b97e4c4546b7f870a3ac624d56c62bfa5cf9
Author: Atin Mukherjee <amukherj at redhat.com>
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 at redhat.com>
    Reviewed-on: http://review.gluster.org/11798
    Reviewed-by: Avra Sengupta <asengupt at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Anand Nekkunti <anekkunt at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaushal M <kaushal 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=lqnM9Y16xO&a=cc_unsubscribe