-
Notifications
You must be signed in to change notification settings - Fork 350
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 flaky health trait test #4922
Comments
Would someone please update the labels on this issue? |
@rinaldodev thanks for reporting. What labels do you think it is required? Please also let me know if you are going to work on this so I can assign to you. |
@squakez I believe that one is fine. Yes, you can assign it to me, thanks. |
To bring more clarity to this issue: this appears to be caused by the camel-routes health check reporting as Ready before the routes had some time to load. See https://issues.apache.org/jira/browse/CAMEL-20242. |
@rinaldodev are you planning to work on this for next 2.4 release? Should I add it to the milestone? |
Some more analysis on this flaky test can be found in #5345 which is a duplicate of this one |
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status
- Avoid failing assertion on condition status ready=false due to temporary deployment ready condition status (cherry picked from commit apache/camel-k@1c40a392f)
Fixed with #5346 |
What happened?
While running this test,
I noticed the Integration's Ready condition is true for a while before becoming false,
which in turns makes this assertion fail sometimes,
making the test flaky.
See comment #4922 (comment)
Steps to reproduce
Run this e2e test a few times until it fails.
Relevant log output
Camel K version
2.1.0
The text was updated successfully, but these errors were encountered: