+++ This bug was initially created as a clone of Bug #1537602 +++ The tests fail due to a possible configuration issue. Shyam and I debugged it down to that. Going to disable the test to unblock all the other reviews. --- Additional comment from Worker Ant on 2018-01-23 10:18:46 EST --- REVIEW: https://review.gluster.org/19301 (tests: Disable geo-rep tests) posted (#1) for review on master by Nigel Babu --- Additional comment from Shyamsundar on 2018-01-23 10:24:54 EST --- The test fails in the following runs: https://build.gluster.org/job/centos6-regression/8602/console https://build.gluster.org/job/centos6-regression/8604/console https://build.gluster.org/job/centos6-regression/8607/console https://build.gluster.org/job/centos6-regression/8608/console https://build.gluster.org/job/centos6-regression/8612/console Failure is almost always when checking for which nodes are in "Active" and "Passive" states, 06:58:02 not ok 22 Got "1" instead of "2", LINENUM:83 06:58:02 FAILED COMMAND: 2 check_status_num_rows Passive AND/OR 06:58:02 not ok 37 Got "1" instead of "2", LINENUM:102 06:58:02 FAILED COMMAND: 2 check_status_num_rows Passive On checking slave25 and rerunning this test (from a fresh clone of the sources etc.) post step in line 83 it is noted that the command output looks as follows, [root@slave25 ~]# gluster volume geo-replication master 127.0.0.1::slave status detail MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ENTRY DATA META FAILURES CHECKPOINT TIME CHECKPOINT COMPLETED CHECKPOINT COMPLETION TIME ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ slave25.cloud.gluster.org master /d/backends/master1 root 127.0.0.1::slave slave25.cloud.gluster.org Active Changelog Crawl 2018-01-23 14:17:38 7 0 0 0 N/A N/A N/A slave25.cloud.gluster.org master /d/backends/master2 root 127.0.0.1::slave N/A Faulty N/A N/A N/A N/A N/A N/A N/A N/A N/A slave25.cloud.gluster.org master /d/backends/master3 root 127.0.0.1::slave N/A Initializing... N/A N/A N/A N/A N/A N/A N/A N/A N/A slave25.cloud.gluster.org master /d/backends/master4 root 127.0.0.1::slave slave25.cloud.gluster.org Active Changelog Crawl 2018-01-23 14:17:38 9 0 0 0 N/A N/A N/A The above never recovers, and so is not a timing issue per-se. Can someone from the geo-rep team take a look at the logs from those runs to determine what is going wrong and why is the status "Faulty" or Initializing" as that seem to be th estart of the test failure. --- Additional comment from Worker Ant on 2018-01-23 21:11:52 EST --- COMMIT: https://review.gluster.org/19301 committed in master by \"Nigel Babu\" <nigelb> with a commit message- tests: Disable geo-rep tests These tests are prone to issues at the moment that need further debugging and fixing. BUG: 1537602 Change-Id: Ic59ca620925c6f43948b8a751eaddb571b791969 Signed-off-by: Nigel Babu <nigelb>
REVIEW: https://review.gluster.org/19363 (tests: Disable geo-rep tests) posted (#1) for review on release-4.0 by Nigel Babu
COMMIT: https://review.gluster.org/19363 committed in release-4.0 by $GERRIT_PATCHSET_UPLOADER with a commit message- tests: Disable geo-rep tests These tests are prone to issues at the moment that need further debugging and fixing. > BUG: 1537602 > Change-Id: Ic59ca620925c6f43948b8a751eaddb571b791969 > Signed-off-by: Nigel Babu <nigelb> (cherry picked from commit 5cbe21b1ddf6eae4782afa33ce841fc4aa195974) Change-Id: I5ccb7751203526082a6f71fa96cff47b56372bf7 BUG: 1539657 Signed-off-by: Nigel Babu <nigelb>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.0.0, please open a new bug report. glusterfs-4.0.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/