CI: ConformanceGKE: multiple connectivity tests failed

[twpayne]

Observed in this run in #16914 (which only touches test infrastructure, not Cilium's code).

📋 Test Report
❌ 4/9 tests failed (9/81 actions), 0 tests skipped, 0 scenarios skipped:
Test [allow-all]:

Error: Connectivity test failed: 4 tests failed
  ❌ allow-all/pod-to-service/curl-1: cilium-test/client2-666976c95b-m996g (192.168.79.102) -> cilium-test/echo-same-node (echo-same-node:8080)
  ❌ allow-all/pod-to-world/http-to-cilium-io: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> cilium-io-http (cilium.io:80)
  ❌ allow-all/pod-to-world/http-to-jenkins-cilium: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> jenkins-cilium-io-http (jenkins.cilium.io:80)
Test [to-fqdns]:
  ❌ to-fqdns/pod-to-world/http-to-cilium-io: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> cilium-io-http (cilium.io:80)
Test [to-entities-world]:
  ❌ to-entities-world/pod-to-world/http-to-jenkins-cilium: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> jenkins-cilium-io-http (jenkins.cilium.io:80)
Test [no-policies]:
  ❌ no-policies/pod-to-world/http-to-cilium-io: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> cilium-io-http (cilium.io:80)
  ❌ no-policies/pod-to-world/http-to-jenkins-cilium: cilium-test/client-7b7bf54b85-jpwq5 (192.168.50.253) -> jenkins-cilium-io-http (jenkins.cilium.io:80)
  ❌ no-policies/pod-to-service/curl-1: cilium-test/client2-666976c95b-m996g (192.168.79.102) -> cilium-test/echo-same-node (echo-same-node:8080)
  ❌ no-policies/pod-to-service/curl-2: cilium-test/client2-666976c95b-m996g (192.168.79.102) -> cilium-test/echo-other-node (echo-other-node:8080)
Error: Process completed with exit code 1.

logs_154373.zip
cilium-sysdump-out.zip.zip

Possibly similar to #16096.

[errordeveloper]

I think this is same as #16938.

[joestringer]

I see a couple of different paths here, anything with a destination of cilium-io-http or jenkins-cilium-io-http seems likely to overlap with #16938. The "echo-same-node" / "echo-other-node" should be entirely different though, I would suggest digging further there if we are still observing regular flakes.

[Weil0ng]

Stated to see similar failures in PR #17308

📋 Test Report
❌ 1/11 tests failed (1/110 actions), 0 tests skipped, 0 scenarios skipped:
Test [to-entities-world]:
  ❌ to-entities-world/pod-to-world/http-to-jenkins-cilium-1: cilium-test/client2-666976c95b-mcgf9 (10.244.1.108) -> jenkins-cilium-io-http (jenkins.cilium.io:80)
Error: Process completed with exit code 1.

[github-actions]

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

[github-actions]

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