christophd opened a new issue, #5345: URL: https://github.com/apache/camel-k/issues/5345
### What happened? The E2E test TestHealthTrait is flaky due to failing integration ready condition assertion in [health_test.go#L366](https://github.com/apache/camel-k/blob/main/e2e/common/traits/health_test.go#L366) The E2E test starts an integration that should never become ready due to health traits. But at some point the Integration condition status is `ready=true` because for a short term period the Deployment ready state is reflected in the status: ``` - firstTruthyTime: "2024-04-09T20:36:38Z" lastTransitionTime: "2024-04-09T20:36:38Z" lastUpdateTime: "2024-04-09T20:36:38Z" message: 1/1 ready replicas reason: DeploymentReady status: "True" type: Ready ``` Shortly after that the Integration controller monitor will set the condition status to `ready=false` because of the health trait evaluation. This means there is a racing condition on the Integration ready status that causes the test to be flaky ### Steps to reproduce See https://github.com/apache/camel-k/actions/runs/8620813154/job/23630392501?pr=5342 ### Relevant log output ```shell Camel K installed in namespace test-ce148498-46dd-4778-bf93-496d290c5607 health_test.go:366: Failed after 9.120s. Expected <v1.ConditionStatus>: True to equal <v1.ConditionStatus>: False ``` ### Camel K version 2.3.0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
