-
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
Sidecar injection failures #1648
Comments
Which version are you using? 1.28.0? or is this with master? |
Latest master as of now (e0c53a5) |
I was debugging this issue, and it seems like this happens because we changed the way we auto instrumented the query deployment, when the deployment is starting it mutates its state, and when we try to update the deployment with the sidecar, it throws this kind of errors. I saw this before in other injection scenarios as well. I can get the object one more time before the update to make sure I have the latest version, but I find this problematic and hard to solve. I think the only definitive solution will be to use webhook mutator. |
same error in 1.29.0
|
after upgrading jaeger-operator from 1.29 to 1.32 i get the same error
|
I am also having the same error. I am using the very latest version of Jaeger-operator which is 1.34. Error which i am getting looks like
Any suggestions what should i do? |
How will a webhook mutator be used here? I think I am not aware of it, of how it will be used. |
Does the error message show an effect? My guess is, when a deployment is created, it passes through the provided webhook to modify the pod spec. |
Probably we can ignore this error and simply trigger the Jaeger reconciler again to be on the safe side. |
What command can I use to trigger the reconciler again? |
I am unable to see this service on my Jaeger UI which is properly up and running and shows the jaegery-query service also. The pods were perfectly running still i could not see it on the UI. Went through the logs of jaeger-operator and saw this error over here. Assumed that it can be because this error. |
Its done automatically. No action need.
I assume there is no correlation. But i will look into it. |
Having same problem - jaeger-operator v1.36.0. Yesterday was updated along with the cluster components. Previously on v1.35.0 there were no problems. Reverting the version didn't fix the problem |
@violinorg, could you provide some log output? |
Probably the log output is similar to the other reports. Looks like the logging is causing confusion, maybe we should change the reported message and/or only log on debug level. What do you think? |
If it is not raising a real issue... |
@iblancasa yes of course time="2022-08-26T12:40:04Z" level=error msg="Operation cannot be fulfilled on deployments.apps \"r882-dcc95-observability-tracing-demo\": the object has been modified; please apply your changes to the latest version an │
│ 1.6615176046172814e+09 ERROR Reconciler error {"controller": "jaeger", "controllerGroup": "jaegertracing.io", "controllerKind": "Jaeger", "jaeger": {"name":"observability-t1260-3f32c-jaeger-operator-jaeger","n │
│ sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem │
│ /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:273 |
@frzifus I'm not sure but it seems this message is not printed by Jaeger Operator but by the inherit logger. |
When installing the simple-prod example in the
monitoring
namespace, the following is shown in the logs:The text was updated successfully, but these errors were encountered: