-
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
Failing integration does not report error condition #3412
Comments
Hey @astefanutti, I had a first look at this, but I am not able to figure it out where it is failing. Do you have some suggestion to places I should look for a fix? I had a look at the code and I think that error conditions should be captured by
|
Is this somewhere like this that is relevant to the issue? |
Thanks @tadayosi. I am not sure what is the expected behavior. I mean, I'm assuming that a failing IntegrationKit build will take care to turn the Integration which owns it as errored as well but I don't know where it used to happen. There were several refactoring in the past, so, likely we missed something. Also we need to introduce an E2E test to take care of this situation and avoid any future regression. |
@squakez as you pointed it out, the integration phase is set to error when the kit fails in:
I suspect this works, but the integration phase gets overwritten later with: camel-k/pkg/controller/integration/monitor.go Line 230 in c3b9c9b
For some reasons, the phase is not set to error while introspecting the underlying deployment / pods. That being said, it may be more robust to force the phase to error in that case, which would likely provide a better error message. |
I've gone deep in this and found the responsible is this check here: camel-k/pkg/controller/integration/kits.go Lines 117 to 121 in 132dceb
|
Error state. Closes apache#3412
Error state. Closes apache#3412
Any failing integration, ie
kamel run -d mvn:com.example:nonexistent:1.0 Hello.java
will correctly set the error on IntegrationKit, but won't do on Integration, resulting the Integration in aBuilding Kit
state even if it failed:The text was updated successfully, but these errors were encountered: