Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CI: ConformanceIngress (Shared LB): expected status code 200 but 503 was returned #21710

Closed
christarazi opened this issue Oct 12, 2022 · 4 comments · Fixed by #22673
Closed

CI: ConformanceIngress (Shared LB): expected status code 200 but 503 was returned #21710

christarazi opened this issue Oct 12, 2022 · 4 comments · Fixed by #22673
Assignees
@sayboras
Labels
area/CI Continuous Integration testing issue or flake area/servicemesh GH issues or PRs regarding servicemesh ci/flake This is a known failure that occurs in the tree. Please investigate me!

Comments

@christarazi
Copy link
Member

CI failure

--- Failed steps:

  Scenario Outline: An Ingress with no rules should send all requests to the default backend # features/default_backend.feature:21
    Then the response status-code must be 200 # features/default_backend.feature:23
      Error: expected status code 200 but 503 was returned

https://github.com/cilium/cilium/actions/runs/3221405223

Sysdump: https://github.com/cilium/cilium/suites/8703041754/artifacts/392928973
@christarazi christarazi added area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! labels Oct 12, 2022
@christarazi christarazi mentioned this issue Oct 12, 2022
Merged
@sayboras
Copy link
Member

This might be fixed as part of #21749.

@sayboras
Copy link
Member

As #21749 is merged, we can monitor this issue for some more time.

@sayboras
Copy link
Member

sayboras commented Nov 1, 2022

the issue is still happening in below run.

https://github.com/cilium/cilium/actions/runs/3364280585/jobs/5578447338

@youngnick
Copy link
Contributor

I agree there's a good chance of a collision here with the Gateway API logic which dictates 503s for no match.

@youngnick youngnick added the area/servicemesh GH issues or PRs regarding servicemesh label Nov 8, 2022
@julianwiedmann julianwiedmann mentioned this issue Nov 28, 2022
Merged
@sayboras sayboras mentioned this issue Dec 11, 2022
Merged
sayboras added a commit to sayboras/cilium that referenced this issue Dec 11, 2022
@sayboras
gha: Add retry mechanism for conformance ingress (shared)
a47ec90 
This is to make sure http retry was done as part of the test.

Fixes: cilium#21710
Fixes: cilium#21993

Signed-off-by: Tam Mach <tam.mach@cilium.io>
aanm pushed a commit that referenced this issue Dec 13, 2022
@sayboras @aanm
gha: Add retry mechanism for conformance ingress (shared)
303d2e7 
This is to make sure http retry was done as part of the test.

Fixes: #21710
Fixes: #21993

Signed-off-by: Tam Mach <tam.mach@cilium.io>
joestringer pushed a commit to joestringer/cilium that referenced this issue Dec 21, 2022
@sayboras @joestringer
gha: Add retry mechanism for conformance ingress (shared)
093a1be 
[ upstream commit 303d2e7 ]

This is to make sure http retry was done as part of the test.

Fixes: cilium#21710
Fixes: cilium#21993

Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Joe Stringer <joe@cilium.io>
joestringer pushed a commit that referenced this issue Dec 22, 2022
@sayboras @joestringer
gha: Add retry mechanism for conformance ingress (shared)
fc1e81a 
[ upstream commit 303d2e7 ]

This is to make sure http retry was done as part of the test.

Fixes: #21710
Fixes: #21993

Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Joe Stringer <joe@cilium.io>
YutaroHayakawa pushed a commit to YutaroHayakawa/cilium that referenced this issue Mar 17, 2023
@sayboras @michi-covalent
gha: Add retry mechanism for conformance ingress (shared)
02211f0 
[ upstream commit 303d2e7 ]

This is to make sure http retry was done as part of the test.

Fixes: cilium#21710
Fixes: cilium#21993

Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Joe Stringer <joe@cilium.io>
Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sayboras sayboras

Labels
area/CI Continuous Integration testing issue or flake area/servicemesh GH issues or PRs regarding servicemesh ci/flake This is a known failure that occurs in the tree. Please investigate me!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

gha: Add retry mechanism for conformance ingress (shared) sayboras/cilium
3 participants
@christarazi @sayboras @youngnick