Skip to content

CI: Ingress Conformance Test: An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred #30281

@learnitall

Description

@learnitall

CI failure

Name

Ingress Conformance Test (Without_XDP, true, false, disabled, dedicated, false): An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred

Logs

Scenario: An Ingress with mixed path rules should send traffic to the matching backend service where Exact is preferred # features/path_rules.feature:174
    When I send a "GET" request to "http://mixed-path-rules/foo"                                                          # feature.go:94 -> iSendARequestTo
    timeout while waiting after 6 attempts, 0/3 sucessess
    Then the response status-code must be 200                                                                             # feature.go:102 -> theResponseStatuscodeMustBe
    And the response must be served by the "foo-exact" service           

Sysdump

cilium-sysdump-out.zip

Link

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CIContinuous Integration testing issue or flakearea/servicemeshGH issues or PRs regarding servicemeshci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions