-
Notifications
You must be signed in to change notification settings - Fork 350
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.
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
Integration stuck at Building Kit if properties are defined, but the runtime is not #6006
Comments
Can you verify the status of IntegrationKit and Build resources as well? I think that you have some building against the default Camel version (3.8.1 in Camel K 2.4.0) which are failing for some reason. Likely, setting the runtime version would reuse the existing Kit. |
@squakez sure. Here are some more details. My Integrationplatform is setup so the default runtime is 3.2.3:
This is the status of the kit, build and Integration:
And these are the final log messages from the operator:
I'll test with other default runtimes and let you know if the behavior changes. |
Using either runtime 3.8.1 or 3.15.0 as default doesn't change the results. |
Also, I have deleted all the Integration Kits and restarted the operator before each test. |
Is there any warning condition in the Integration resource? Can you provide the |
@squakez I did some investigation and have some interesting news: I changed the operator log level to debug and with that I see these messages in the operator log:
I tracked the code and realized this happens when the Matches function on the CamelTrait returns false:
I added some debugging messages and found out that Also, I have eventually seen
and decided to check the locations where it can get the runtime from. Here are the yamls for the platform:
and the integration:
|
What happened?
Consider the following Integration:
When I apply it to my cluster, the Integrations remains stuck at Building Kit:
If I include the runtimeVersion at the camel trait:
or remove the trait completely, the integration build finishes successfully.
I checked the operator log and there is no error message related to the trait. Logs look good as usual.
Steps to reproduce
No response
Relevant log output
No response
Camel K version
2.4.0
The text was updated successfully, but these errors were encountered: