Skip to content

CI: Pod-to-ingress-service-allow-ingress-identity exit 22 failure #39472

@YutaroHayakawa

Description

@YutaroHayakawa

CI failure

❌ command "curl --silent --fail --show-error --connect-timeout 2 --max-time 10 -w %{local_ip}:%{local_port} -> %{remote_ip}:%{remote_port} = %{response_code}\n --output /dev/null [http://cilium-ingress-same-node.cilium-test-3:80](http://cilium-ingress-same-node.cilium-test-3/)" failed: command failed (pod=cilium-test-3/client2-6dd74d49c5-nvq98, container=client2): command terminated with exit code 22
...
❌ 1/20 tests failed (1/257 actions), 3 tests skipped, 0 scenarios skipped:
Test [pod-to-ingress-service-allow-ingress-identity]:
  ❌ pod-to-ingress-service-allow-ingress-identity/pod-to-ingress-service:curl-2: cilium-test-3/client2-6dd74d49c5-nvq98 (10.244.3.51) -> cilium-test-3/cilium-ingress-same-node (cilium-ingress-same-node.cilium-test-3:80)
    ⛑️ The following owners are responsible for reliability of the testsuite: 
        - @cilium/sig-lb (pod-to-ingress-service)
        - @cilium/ci-structure (.github/workflows/tests-e2e-upgrade.yaml)

Link: https://github.com/cilium/cilium/actions/runs/14935254370/job/41961095656
Sysdump: cilium-sysdump-conn-disrupt-test-cilium-upgrade-12-concurrent-20250509-183950 2.zip

Metadata

Metadata

Assignees

Labels

area/CIContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions