-
Notifications
You must be signed in to change notification settings - Fork 349
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.
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
flaky: FAIL TestE2E/OIDC http_route_with_oidc_authentication #3898
Comments
cc @zhaohuabing |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Now it's the top 1 flaky. |
Looks like it's a xDS sequence issue. Sometimes, the clusters come before the listeners. We had this issue before but it has been fixed in envoyproxy/go-control-plane#752 and envoyproxy/go-control-plane#801. However, it seems like there're still some edge cases that have not been covered.
{
"version_info": "128f48574c7597a14171b86d0843a3b9e4260fa85903ac200b688f95b485cffc",
"cluster": {
"@type": "type.googleapis.com/envoy.config.cluster.v3.Cluster",
"name": "keycloak_gateway-conformance-infra_80",
.....
"last_updated": "2024-09-30T03:38:17.438Z"
},
....
"error_state": {
"failed_configuration": {
"@type": "type.googleapis.com/envoy.config.listener.v3.Listener",
"name": "gateway-conformance-infra/same-namespace/http",
"last_update_attempt": "2024-09-30T03:38:17.433Z",
"details": "OAuth2 filter: unknown cluster 'keycloak_gateway-conformance-infra_80' in config. Please specify which cluster to direct OAuth requests to."
|
|
Yes, sometimes the cluter arrives behind the listener configuration, that's why we got this error. |
@zhaohuabing is this because we moved to the |
@arkodg I remember this flaky existed before the |
ref https://github.com/envoyproxy/gateway/actions/runs/10002832453/job/27649851258#step:6:56104
The text was updated successfully, but these errors were encountered: