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.

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

Operation cannot be fulfilled on horizontalpodautoscalers.autoscaling \"jaeger-operator-jaeger-collector\" / failed to apply the changes #1982

Open
sta-szek opened this issue Jul 5, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@sta-szek
Copy link

sta-szek commented Jul 5, 2022

Describe the bug
I got errors:

time="2022-07-04T10:28:54Z" level=error msg="failed to apply the changes" error="Operation cannot be fulfilled on deployments.apps \"jaeger-operator-jaeger-query\": the object has been modified; please apply your changes to the latest version and try again" execution="2022-07-04 10:28:53.755169567 +0000 UTC" instance=jaeger-operator-jaeger namespace=monitoring

1.6569305347026784e+09	ERROR	controller.jaeger	Reconciler error	{"reconciler group": "jaegertracing.io", "reconciler kind": "Jaeger", "name": "jaeger-operator-jaeger", "namespace": "monitoring", "error": "Operation cannot be fulfilled on deployments.apps \"jaeger-operator-jaeger-query\": the object has been modified; please apply your changes to the latest version and try again"}

To Reproduce
Steps to reproduce the behavior:

  1. Just wait, it happens on daily basis

Deployed on K8S, using jaeger-operator:

apiVersion: v1
description: jaeger-operator Helm chart for Kubernetes
name: jaeger-operator
version: 2.32.2
appVersion: 1.34.1
@sta-szek sta-szek added the bug Something isn't working label Jul 5, 2022
@frzifus
Copy link
Member

frzifus commented Jul 8, 2022

HI @sta-szek, does it lead to weird behavior or is it just the message you see?
ctx: #1648 (comment)

@frzifus frzifus self-assigned this Jul 8, 2022
@sta-szek
Copy link
Author

sta-szek commented Oct 4, 2022

hi @frzifus i just saw your question.
basically it restart the pod in our k8s system - looks like jaeger-operator just die in that case.
its not a big deal, since jaeger-operator is not customer facing service and it is also not jaeger UI itself, so we can just mute alert about pod restart and continue.

anyway, would be good to see why it happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants