You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "christophd (via GitHub)" <gi...@apache.org> on 2024/01/10 10:13:01 UTC
[I] 1st Integration after Camel K runtime version update failing [camel-k]
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] 1st Integration after Camel K runtime version update failing [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4776:
URL: https://github.com/apache/camel-k/issues/4776#issuecomment-1884666911
fyi @squakez
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] 1st Integration after Camel K runtime version update failing [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #4776: 1st Integration after Camel K runtime version update failing
URL: https://github.com/apache/camel-k/issues/4776
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] 1st Integration after Camel K runtime version update failing [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4776:
URL: https://github.com/apache/camel-k/issues/4776#issuecomment-1752560480
Closed by #4764
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] 1st Integration after Camel K runtime version update failing [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4776:
URL: https://github.com/apache/camel-k/issues/4776#issuecomment-1884554246
I just experienced the same behavior with Camel K 2.2 and runtimeVersion 3.6.0. After setting the runtime version in the IntegrationPlatform settings the first run integration goes into error state (does not recover from that state) because the camel catalog for 3.6.0 is not available.
The 2nd run of the same integration is successful because in the meantime the catalog has been built and added as a custom resource.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #4776: 1st Integration after Camel K runtime version update failing
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4776:
URL: https://github.com/apache/camel-k/issues/4776#issuecomment-1740471548
Thanks for reporting. Yes, this may be caused by the fact that when the IntegrationPlatform is reconciled it does not create the CamelCatalog straight away. We need to make this happen on IP reconciliation instead of waiting the first Integration run as you are notifying.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] 1st Integration after Camel K runtime version update failing [camel-k]
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd closed issue #4776: 1st Integration after Camel K runtime version update failing
URL: https://github.com/apache/camel-k/issues/4776
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org