From b917974ee922d7a2e079692ad7d6f61f900b37b2 Mon Sep 17 00:00:00 2001 From: Sanju Rakonde Date: Fri, 12 Jul 2019 16:28:04 +0530 Subject: glusterd: do not mark skip_locking as true for geo-rep operations We need to send the commit req to peers in case of geo-rep operations even though it is a no volname operation. In commit phase peers try to set the txn_opinfo which will fail because it is a no volname operation where we don't require a commit phase. We mark skip_locking as true for no volname operations, but we have to give an exception to geo-rep operations, so that they can set txn_opinfo in commit phase. Please refer to detailed RCA at the bug: 1729463 fixes: bz#1729463 Change-Id: I9f2478b12a281f6e052035c0563c40543493a3fc Signed-off-by: Sanju Rakonde --- tests/00-geo-rep/01-georep-glusterd-tests.t | 3 +++ 1 file changed, 3 insertions(+) (limited to 'tests/00-geo-rep') diff --git a/tests/00-geo-rep/01-georep-glusterd-tests.t b/tests/00-geo-rep/01-georep-glusterd-tests.t index 2960a55c587..47d5116af26 100644 --- a/tests/00-geo-rep/01-georep-glusterd-tests.t +++ b/tests/00-geo-rep/01-georep-glusterd-tests.t @@ -107,6 +107,9 @@ EXPECT_WITHIN $GEO_REP_TIMEOUT 0 check_keys_distributed #Start_georep TEST $GEOREP_CLI $master $slave start +#check geo-rep status without specifying master and slave volumes +TEST $GEOREP_CLI status + #Start_georep force TEST $GEOREP_CLI $master $slave1 start force -- cgit