Skip to content
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.

Sign up for GitHub

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

Jump to bottom

1st Integration after Camel K runtime version update failing #4776

Closed
christophd opened this issue Sep 29, 2023 · 4 comments · Fixed by #5086
Closed

1st Integration after Camel K runtime version update failing #4776

christophd opened this issue Sep 29, 2023 · 4 comments · Fixed by #5086
Assignees
@christophd
Labels
camel/catalog Related to Camel catalog usage kind/bug Something isn't working
Milestone
2.3.0

Comments

@christophd
Copy link
Contributor

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
@christophd christophd added the kind/bug Something isn't working label Sep 29, 2023
@squakez
Copy link
Contributor

squakez commented Sep 29, 2023

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.

@squakez squakez added the camel/catalog Related to Camel catalog usage label Sep 29, 2023
@squakez squakez added this to the 2.1.0 milestone Sep 29, 2023
@squakez
Copy link
Contributor

squakez commented Oct 9, 2023

Closed by #4764

@squakez squakez closed this as completed Oct 9, 2023
@christophd
Copy link
Contributor Author

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.

@christophd christophd reopened this Jan 10, 2024
@christophd
Copy link
Contributor Author

fyi @squakez

@squakez squakez modified the milestones: 2.1.0, 2.3.0 Jan 12, 2024
@christophd christophd self-assigned this Jan 18, 2024
christophd added a commit to christophd/camel-k that referenced this issue Jan 19, 2024
@christophd
fix(apache#4776): Fix catalog loading in camel trait
1c3c1df 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution
@christophd christophd mentioned this issue Jan 19, 2024
Merged
christophd added a commit to christophd/camel-k that referenced this issue Jan 22, 2024
@christophd
fix(apache#4776): Fix catalog loading in camel trait
84c4977 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution
christophd added a commit that referenced this issue Jan 22, 2024
@christophd
fix(#4776): Fix catalog loading in camel trait
2916247 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution
christophd added a commit to christophd/camel-k that referenced this issue Jan 29, 2024
@christophd
fix(apache#4776): Fix catalog loading in camel trait
07e9b93 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution

(cherry picked from commit 2916247)
christophd added a commit that referenced this issue Jan 29, 2024
@christophd
fix(#4776): Fix catalog loading in camel trait
1dee047 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution

(cherry picked from commit 2916247)
squakez pushed a commit to jboss-fuse/camel-k that referenced this issue Jan 29, 2024
@christophd @github-actions
fix(apache#4776): Fix catalog loading in camel trait
d6cf479 
- When new runtime version is used on integration the camel trait creates the catalog if it does not exist already
- Use proper catalog namespace to verify that the catalog resource has been created during the camel trait execution

(cherry picked from commit 2916247)

(cherry picked from commit apache/camel-k@1dee04715)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@christophd christophd

Labels
camel/catalog Related to Camel catalog usage kind/bug Something isn't working
Projects
None yet
Milestone
2.3.0
Development

Successfully merging a pull request may close this issue.

fix(#4776): Fix catalog loading in camel trait christophd/camel-k
2 participants
@christophd @squakez