summaryrefslogtreecommitdiffstats
path: root/rpc
diff options
context:
space:
mode:
authormohit84 <moagrawa@redhat.com>2021-04-23 19:26:49 +0530
committerGitHub <noreply@github.com>2021-04-23 15:56:49 +0200
commitdbbad5d69c73a62888a22adf40901e9a578c6518 (patch)
tree925b996e72687007aeddef5163289d3584146c68 /rpc
parent6a43697a6c2f41336a4ce6b85ea2b50c449fc7d0 (diff)
downloadglusterfs-dbbad5d69c73a62888a22adf40901e9a578c6518.tar.gz
glusterfs-dbbad5d69c73a62888a22adf40901e9a578c6518.tar.xz
glusterfs-dbbad5d69c73a62888a22adf40901e9a578c6518.zip
glusterd: After upgrade on release 9.1 glusterd protocol is broken (#2352)devel
* glusterd: After upgrade on release 9.1 glusterd protocol is broken After upgrade on release-9 glusterd protocol is broken because on the upgraded nodes glusterd is not able to find an actor at expected index in rpc procedure table.The new proc (GLUSTERD_MGMT_V3_POST_COMMIT) was introduced from a patch(https://review.gluster.org/#/c/glusterfs/+/24771/) in the middle due to that index of existing actor is changed on new upgraded nodes glusterd is failing. Solution: Change the proc(GLUSTERD_MGMT_V3_POST_COMMIT) position at last in proc table to avoid an issue. Fixes: #2351 Change-Id: I36575fd4302944336a75a8d4a305401a7128fd84 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Diffstat (limited to 'rpc')
-rw-r--r--rpc/rpc-lib/src/protocol-common.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/rpc/rpc-lib/src/protocol-common.h b/rpc/rpc-lib/src/protocol-common.h
index b18eac68ee..8f4212df52 100644
--- a/rpc/rpc-lib/src/protocol-common.h
+++ b/rpc/rpc-lib/src/protocol-common.h
@@ -309,9 +309,10 @@ enum glusterd_mgmt_v3_procnum {
GLUSTERD_MGMT_V3_PRE_VALIDATE,
GLUSTERD_MGMT_V3_BRICK_OP,
GLUSTERD_MGMT_V3_COMMIT,
- GLUSTERD_MGMT_V3_POST_COMMIT,
GLUSTERD_MGMT_V3_POST_VALIDATE,
GLUSTERD_MGMT_V3_UNLOCK,
+ GLUSTERD_MGMT_V3_POST_COMMIT,
+ /* Always add new proc just before the MGMT_V3_MAXVALUE declartion */
GLUSTERD_MGMT_V3_MAXVALUE,
};