CI: K8sConformance Portmap Chaining Check connectivity-check compliance with portmap chaining

[aanm]

/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Kernel/k8s-1.17-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:512
connectivity-check pods are not ready after timeout
Expected
    <*errors.errorString | 0xc000652760>: {
        s: "timed out waiting for pods with filter  to be ready: 4m0s timeout expired",
    }
to be nil
/usr/local/go/src/reflect/value.go:460

b92c71ed_K8sConformance_Portmap_Chaining_Check_connectivity-check_compliance_with_portmap_chaining.zip

[pchaigno]

The logs have a couple Unable to restore endpoint warnings that may be related:

2020-06-02T21:26:26.374327728Z level=warning msg="Unable to restore endpoint, ignoring" endpointID=2956 error="Kubernetes pod default/ratings-v1-75c477b778-9lsb5 does not exist" k8sPodName=default/ratings-v1-75c477b778-9lsb5 subsys=daemon
[...]
2020-06-02T21:26:26.374458819Z level=warning msg="Unable to restore endpoint, ignoring" endpointID=826 error="Kubernetes pod default/reviews-v1-75cfdb45f-qstbg does not exist" k8sPodName=default/reviews-v1-75cfdb45f-qstbg subsys=daemon
[...]
2020-06-02T21:26:26.374470619Z level=warning msg="Unable to restore endpoint, ignoring" endpointID=980 error="Kubernetes pod default/reviews-v2-6588f4df97-vxbq7 does not exist" k8sPodName=default/reviews-v2-6588f4df97-vxbq7 subsys=daemon
[...]
2020-06-02T21:26:26.374486663Z level=warning msg="Unable to restore endpoint, ignoring" endpointID=1446 error="Kubernetes pod default/details-v1-6df6c569f8-n5bf2 does not exist" k8sPodName=default/details-v1-6df6c569f8-n5bf2 subsys=daemon

I could find a only one other occurrence of this flake on master over the last 14 days: https://jenkins.cilium.io/job/Ginkgo-CI-Tests-k8s1.18-Pipeline/457/testReport/Suite-k8s-1/18/K8sConformance_Portmap_Chaining_Check_connectivity_check_compliance_with_portmap_chaining/. I did not go through all failures in PRs, but those I checked were unrelated.

[nebril]

This happened today on GKE: https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline-GKE/1254/testReport/junit/Suite-k8s-1/14/K8sConformance_Portmap_Chaining_Check_connectivity_check_compliance_with_portmap_chaining/ , I guess we fail in retrieving the filter and it causes the check to fail.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has not seen any activity since it was marked stale. Closing.

[christarazi]

Seen in #15384