[Bugs] [Bug 1544366] Rolling upgrade to 4.0 is broken

bugzilla at redhat.com bugzilla at redhat.com
Mon Feb 19 13:53:10 UTC 2018


--- Comment #6 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19582 committed in release-4.0 by "Anoop C
S" <anoopcs at autistici.org> with a commit message- protcol/client: Insert dummy
clnt-lk-version to avoid upgrade failure

With https://review.gluster.org/#/c/12363/ being merged, we no longer
send client's lk-version to server side and the corresponding check on
server is also removed. But when clients are upgraded prior to servers,
the check for lk-version at server side fails and is reported back to
clients resulting in disconnection.

Since we don't have lock-recovery (lk-version and grace-timeout) logic
anymore in code base our best bet would be to add client's default
lk-version i.e, 1, into the dictionary just to make server side check
pass and continue with remaining SETVOLUME operations.

Change-Id: I441b67bd271d1e9ba9a7c08703e651c7a6bd945b
BUG: 1544366
Signed-off-by: Anoop C S <anoopcs at redhat.com>
(cherry picked from commit c096bec4ec3f3ac33cc0787c60978944792e074e)

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=uaDgTsDTPu&a=cc_unsubscribe

More information about the Bugs mailing list