+++ This bug was initially created as a clone of Bug #1721590 +++ Description of problem: tests/bugs/posix/bug-1040275-brick-uid-reset-on-volume-restart.t is failing Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Run test case tests/bugs/posix/bug-1040275-brick-uid-reset-on-volume-restart.t 2. 3. Actual results: test case tests/bugs/posix/bug-1040275-brick-uid-reset-on-volume-restart.t is failing Expected results: test case should not fail Additional info: --- Additional comment from Mohit Agrawal on 2019-06-18 15:56:44 UTC --- .t is failing and throwing error transport endpoint is not connected at the time of running stat command on mount point after just start the volume. In logs it is showing the client is not able to establish a connection with server so at the running stat command it is failing. To avoid the error needs to wait after just starting the volume. --- Additional comment from Worker Ant on 2019-06-18 16:01:10 UTC --- REVIEW: https://review.gluster.org/22893 (test: test bug-1040275-brick-uid-reset-on-volume-restart.t is failing) posted (#1) for review on master by MOHIT AGRAWAL --- Additional comment from Worker Ant on 2019-06-25 05:22:32 UTC --- REVIEW: https://review.gluster.org/22893 (test: Fix spurious failures in bug-1040275-brick-uid-reset-on-volume-restart.t) merged (#6) on master by Amar Tumballi
REVIEW: https://review.gluster.org/23017 (test: Fix spurious failures in bug-1040275-brick-uid-reset-on-volume-restart.t) posted (#1) for review on release-7 by MOHIT AGRAWAL
REVIEW: https://review.gluster.org/23017 (test: Fix spurious failures in bug-1040275-brick-uid-reset-on-volume-restart.t) merged (#1) on release-7 by MOHIT AGRAWAL