Le jeudi 04 avril 2019 à 16:13 +0530, Atin Mukherjee a écrit : > 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. The firewall didn't change, and since the start has a line: "-A INPUT -i lo -j ACCEPT", so all traffic on the localhost interface work. (I am not even sure that netfilter do anything meaningful on the loopback interface, but maybe I am wrong, and not keen on looking kernel code for that). Ping seems to work fine as well, so we can exclude a routing issue. Maybe we should look at the socket, does it listen to a specific address or not ? > *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-infra mailing list > Gluster-infra@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-infra -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
