-
Notifications
You must be signed in to change notification settings - Fork 347
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
workaroud for the flaky oidc e2e test #4603
base: main
Are you sure you want to change the base?
Conversation
7bbdd8e
to
83e4971
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4603 +/- ##
==========================================
+ Coverage 65.43% 65.45% +0.02%
==========================================
Files 211 211
Lines 31904 31904
==========================================
+ Hits 20875 20883 +8
+ Misses 9784 9778 -6
+ Partials 1245 1243 -2 ☔ View full report in Codecov by Sentry. |
83e4971
to
e5f3897
Compare
Signed-off-by: Huabing Zhao <[email protected]>
e5f3897
to
21fb4f1
Compare
Signed-off-by: Huabing Zhao <[email protected]>
// restart the envoy proxy to recover from the error, this is a workaround for the flaky test: https://github.com/envoyproxy/gateway/issues/3898 | ||
// TODO: we should investigate the root cause of the flakiness and remove this workaround | ||
proxyLabel := map[string]string{"gateway.envoyproxy.io/owning-gateway-name": "same-namespace"} | ||
err := suite.Client.DeleteAllOf(context.TODO(), &corev1.Pod{}, client.MatchingLabels(proxyLabel), client.InNamespace("envoy-gateway-system")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we force a rollout/restart instead of deleting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesnt matter here. We just need to restart the Envoy pod to repush the xDS.
Restart Envoy to recover from the OIDC test failure. This is just a workaround to reduce the time of e2e test due to the failed OIDC test. We still need to investage the root cause and fix it.
Related issue: #3898
Release Notes: No