Skip to content

CI: inconsistent label cardinality: expected 2 label values but got 4 in []string{"outcome", "fail", "failure_type", "transient"} #40801

@behzad-mir

Description

@behzad-mir

CI failure

 Failure in Spec Teardown (AfterEach) [154.965 seconds]
K8sDatapathConfig
/home/runner/work/cilium/cilium/test/ginkgo-ext/scopes.go:461
  Host firewall
  /home/runner/work/cilium/cilium/test/ginkgo-ext/scopes.go:461
    With native routing and endpoint routes [AfterEach]
    /home/runner/work/cilium/cilium/test/ginkgo-ext/scopes.go:515

    Found 2 io.cilium/app=operator logs matching list of errors that must be investigated:
    2025-07-29T20:54:43.574325395Z panic: inconsistent label cardinality: expected 2 label values but got 4 in []string{"outcome", "fail", "failure_type", "transient"}
    2025-07-29T20:55:07.557908302Z panic: inconsistent label cardinality: expected 2 label values but got 4 in []string{"outcome", "fail", "failure_type", "transient"}

The issue is experienced in the CI run:

https://github.com/cilium/cilium/actions/runs/16606958645/job/46981230989

PR link

#37568

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CIContinuous Integration testing issue or flakearea/metricsImpacts statistics / metrics gathering, eg via Prometheus.area/operatorImpacts the cilium-operator componentci/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