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 https://review.gluster.org/#/c/glusterfs/+/22501/ & https://build.gluster.org/job/centos7-regression/5382/ 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.
*15:51:21* Number of Peers: 2*15:51:21* *15:51:21* Hostname: 127.1.1.2*15:51:21* Uuid: 0e689ca8-d522-4b2f-b437-9dcde3579401*15:51:21* State: Accepted peer request (Connected)*15:51:21* *15:51:21* Hostname: 127.1.1.3*15:51:21* Uuid: a83a3bfa-729f-4a1c-8f9a-ae7d04ee4544*15:51:21* State: Accepted peer request (Connected)
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
