-
Notifications
You must be signed in to change notification settings - Fork 703
Fix the upgrade e2e test flakiness #5041
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
Fix the upgrade e2e test flakiness #5041
Conversation
skriss
left a comment
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.
Thanks for this @relu!
7c20179 to
d1a2b42
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5041 +/- ##
=======================================
Coverage 77.49% 77.49%
=======================================
Files 138 138
Lines 16904 16904
=======================================
Hits 13099 13099
Misses 3550 3550
Partials 255 255 |
8847532 to
068acd5
Compare
The upgrade e2e test can fail in some situations because the envoy waiter is incorrectly returning true before the StatefulSet even manages to finish the rollout since it only checks the StatefulSet state on properties that are inconsistently populated due to timing differences. This fix addressed that by using a similar condition validation method as the one already used for the Contour Deployment rollout. Signed-off-by: Aurel Canciu <[email protected]>
068acd5 to
9bc5296
Compare
skriss
left a comment
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.
LGTM, will leave for @sunjayBhatia. Thanks @relu!
The upgrade e2e test can fail in some situations because the envoy waiter is incorrectly returning true before the StatefulSet even manages to finish the rollout since it only checks the StatefulSet state on properties that are inconsistently populated due to timing differences. This fix addressed that by using a similar condition validation method as the one already used for the Contour Deployment rollout. Signed-off-by: Aurel Canciu <[email protected]> Signed-off-by: yy <[email protected]>
The upgrade e2e test can fail in some situations because the envoy waiter is incorrectly returning true before the StatefulSet even manages to finish the rollout since it only checks the StatefulSet state on properties that are inconsistently populated due to timing differences. This fix addressed that by using a similar condition validation method as the one already used for the Contour Deployment rollout. Signed-off-by: Aurel Canciu <[email protected]> Signed-off-by: yy <[email protected]>
The upgrade e2e test can fail in some situations because the envoy waiter is incorrectly returning true before the StatefulSet even manages to finish the rollout since it only checks the StatefulSet state on properties that are inconsistently populated due to timing differences. This fix addressed that by using a similar condition validation method as the one already used for the Contour Deployment rollout. Signed-off-by: Aurel Canciu <[email protected]>
The upgrade e2e test can fail in some situations because the envoy waiter is incorrectly returning true before the StatefulSet even manages to finish the rollout since it only checks the StatefulSet state on properties that are inconsistently populated due to timing differences.
This fix addressed that by using a similar condition validation method as the one already used for the Contour Deployment rollout.