squakez commented on issue #5161: URL: https://github.com/apache/camel-k/issues/5161#issuecomment-1956540607
I think the problem may have been caused by the introduction of `.status.trait`. Whenever there is an update on the Integration, for some reason we are updating it twice. See the Pods evolution: ``` test-5b65c6f9f-s5hwr 1/1 Running 0 4s test-7c7bb6f749-5lgk8 0/1 Pending 0 0s test-7c7bb6f749-5lgk8 0/1 Pending 0 0s test-7c7bb6f749-5lgk8 0/1 ContainerCreating 0 1s test-7c7bb6f749-5lgk8 0/1 Terminating 0 1s test-57c789c9fd-fcv42 0/1 Pending 0 0s test-57c789c9fd-fcv42 0/1 Pending 0 0s test-57c789c9fd-fcv42 0/1 ContainerCreating 0 0s test-57c789c9fd-fcv42 1/1 Running 0 1s test-7c7bb6f749-5lgk8 1/1 Terminating 0 2s test-5b65c6f9f-s5hwr 1/1 Terminating 0 12s test-5b65c6f9f-s5hwr 0/1 Terminating 0 13s test-5b65c6f9f-s5hwr 0/1 Terminating 0 13s test-5b65c6f9f-s5hwr 0/1 Terminating 0 13s test-7c7bb6f749-5lgk8 0/1 Terminating 0 3s test-7c7bb6f749-5lgk8 0/1 Terminating 0 3s test-7c7bb6f749-5lgk8 0/1 Terminating 0 3s ``` I need to have a further look to solve this regression. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
