Code change:
zero := int64(0) <ins> // Create a pod to check the conntrack entries on the host node // It mounts the host /proc/net folder to be able to access // the nf_conntrack file with the host conntrack entries privileged := true hostExecPod := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      "e2e-net-exec", Namespace: fr.Namespace.Name, Labels:    map[string]string{"app": "e2e-net-exec"}, }, Spec: v1.PodSpec{ HostNetwork: true, NodeName:    clientNodeInfo.name, Containers: []v1.Container{ { Name:            "e2e-net-exec", Image:           kubeProxyE2eImage, ImagePullPolicy: "Always", Args:            []string{"pause"}, VolumeMounts: []v1.VolumeMount{ { Name:      "proc-net", MountPath: "/rootfs/proc/net", ReadOnly:  true, }, }, SecurityContext: &v1.SecurityContext{ Privileged: &privileged, }, }, }, Volumes: []v1.Volume{ { Name: "proc-net", VolumeSource: v1.VolumeSource{ HostPath: &v1.HostPathVolumeSource{ Path: "/proc/net", }, }, }, }, TerminationGracePeriodSeconds: &zero, }, } fr.PodClient().CreateSync(hostExecPod) defer fr.PodClient().DeleteSync(hostExecPod.Name, &metav1.DeleteOptions{}, framework.DefaultPodDeletionTimeout) </ins> // Some distributions (Ubuntu 16.04 etc.) don't support the proc file. <del> _, err = e2essh.IssueSSHCommandWithResult( "ls /proc/net/nf_conntrack", framework.TestContext.Provider, clientNodeInfo.node) </del> <ins> _, err = framework.RunHostCmd(fr.Namespace.Name, "e2e-net-exec", "ls /rootfs/proc/net/nf_conntrack") </ins> if err != nil && strings.Contains(err.Error(), "No such file or directory") { framework.Skipf("The node %s does not support /proc/net/nf_conntrack", clientNodeInfo.name) } framework.ExpectNoError(err) <ins> // Create the client and server pods </ins> clientPodSpec := &v1.Pod{ ObjectMeta: metav1.ObjectMeta{ Name:      "e2e-net-client",

Related discussion:
text: Which jobs are failing: kops-aws and many other jobs Which test(s) are failing: This isn't the actual test, but the text we're consistently seeing is Since when has it been failing: Testgrid links: (ref: ) Reason for failure: TBD Anything else we need to know: Very rarely tests pass when one of the tests passes: Seems related to , that was merged about the same time:
/sig cluster-lifecycle /sig aws
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /sig cluster-lifecycle /sig aws Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority critical-urgent this is merge blocking
/assign /cc /cc /cc
The PR we think we want to revert
is also failing, I don't think this is aws-specific
/cc
/assign
it failed with kind too :/ with the same message
Opened to revert
/unassign /sig network /sig testing /remove-sig cluster-lifecycle
/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. ‍
This may be the actual cause PR to address But we're going with revert first to be sure we've identified the offending PR
I think I've identified the root cause
Revert brought us back to green: Awaiting root cause fix
/remove-triage unresolved
/reopen merged but we're now seeing multiple tests fail since it merged Looking at it went red between these commits:
Reopened this issue. <detailsIn response to : /reopen merged but we're now seeing multiple tests fail since it merged Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
is an attempt to fix
reverting in
is the failure cluster I suspect will go down once the revert goes in
/close Failure cluster has gone down, calling this done <img width="998" alt="Screen Shot 2020-01-10 at 9 56 17 AM" src="https://user-"
Closing this issue.