Skip to content

CI: Conformance Ginkgo calls cilium-dbg during upgrade tests on Cilium versions that don't support it #29195

@gandro

Description

@gandro

CI failure

Observed in https://github.com/cilium/cilium/actions/runs/6878246033/job/18707557137#step:16:392

 Fetching command output from pods [cilium-7pvbx cilium-bv9gd]
cmd: kubectl exec -n kube-system cilium-7pvbx -c cilium-agent -- cilium-dbg endpoint list
Exitcode: 1 
Err: exit status 1
Stdout:
 	 
Stderr:
 	 error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "c9d4c3fe67af8d1065018796128991b7fd3ebcfd931f67f50a4de3952b8671b5": OCI runtime exec failed: exec failed: unable to start container process: exec: "cilium-dbg": executable file not found in $PATH: unknown

This happens during Tests upgrade and downgrade from a Cilium stable image to master, i.e. we deploy Cilium v1.14 and if that has any errors, we then call cilium-dbg endpoint list, which will not work against Cilium v1.14

Note: This does not cause CI to fail, so this is not a flake. It's a bug in our CI, but it doesn't make tests fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CIContinuous Integration testing issue or flake

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions