christophd opened a new issue, #4776: URL: https://github.com/apache/camel-k/issues/4776
### What happened? In case users update the Camel K runtime version in the IntegrationPlatform (e.g. from 2.x to 3.2.0 in order to update to Camel v4) the 1st Integration that is run after the version change is failing. The error reported is CamelCatalog not found. It seems that the new CamelCatalog is built when the 1st Integration is run. The racing condition between building the catalog and Integration building the kit is causing the error. As far as I could see the error state did not recover and I had to restart the Integration once again. After restart everything has worked as expected and the new catalog with new runtime version has been used. ### Steps to reproduce 1. Install Camel K 2.0.1 2. Update the Camel K runtime version in the IntegrationPlatform to 3.2.0 3. Start an Integration 4. See the Integration failing and going into error state ### Relevant log output _No response_ ### Camel K version 2.0.1 -- 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
