<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Based on what I have seen that any multi node test case will fail and the above one is picked first from that group and If I am correct none of the code fixes will go through the regression until this is fixed. I suspect it to be an infra issue again. If we look at <a href="https://review.gluster.org/#/c/glusterfs/+/22501/">https://review.gluster.org/#/c/glusterfs/+/22501/</a> &amp; <a href="https://build.gluster.org/job/centos7-regression/5382/">https://build.gluster.org/job/centos7-regression/5382/</a> peer handshaking is stuck as 127.1.1.1 is unable to receive a response back, did we end up having firewall and other n/w settings screwed up? The test never fails locally.<br></div><div dir="ltr"><br></div><div dir="ltr"><pre class="gmail-console-output"><span class="gmail-timestamp"><b>15:51:21</b> </span>Number of Peers: 2
<span class="gmail-timestamp"><b>15:51:21</b> </span>
<span class="gmail-timestamp"><b>15:51:21</b> </span>Hostname: 127.1.1.2
<span class="gmail-timestamp"><b>15:51:21</b> </span>Uuid: 0e689ca8-d522-4b2f-b437-9dcde3579401
<span class="gmail-timestamp"><b>15:51:21</b> </span>State: Accepted peer request (Connected)
<span class="gmail-timestamp"><b>15:51:21</b> </span>
<span class="gmail-timestamp"><b>15:51:21</b> </span>Hostname: 127.1.1.3
<span class="gmail-timestamp"><b>15:51:21</b> </span>Uuid: a83a3bfa-729f-4a1c-8f9a-ae7d04ee4544
<span class="gmail-timestamp"><b>15:51:21</b> </span>State: Accepted peer request (Connected)<br><br><br></pre></div></div></div></div>