-
Notifications
You must be signed in to change notification settings - Fork 345
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
Nil pointer dereference tracing trait #3205
Labels
Comments
Thanks for reporting. That trace appears on some |
This is on the operator log. |
@squakez could this be assigned to me? T for thanks! |
Sure, thanks a lot! |
@Gre8t Since it's been inactive for long time, let me take it over. |
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jul 21, 2022
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jul 21, 2022
This issue happened when an trait was enabled at IntegrationPlatform which is implemented not considering possible absence of Integration. Fix apache#3205
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jul 22, 2022
This issue happened when an trait was enabled at IntegrationPlatform which is implemented not considering possible absence of Integration. Fix apache#3205
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jul 22, 2022
This issue happened when an trait was enabled at IntegrationPlatform which is implemented not considering possible absence of Integration. Fix apache#3205
tadayosi
added a commit
that referenced
this issue
Jul 22, 2022
This issue happened when an trait was enabled at IntegrationPlatform which is implemented not considering possible absence of Integration. Fix #3205
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having issues with trying to run an Integration that uses the tracing trait with the following errors in the operator.
We're currently running the helm-operator, but I tried this with the 1.8.x operator-channel on Openshift with the same issue.
This is the following setup for the integration
And we have the following IntegrationPlatform applied
The text was updated successfully, but these errors were encountered: