-
Notifications
You must be signed in to change notification settings - Fork 344
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
Lock reconciliation per instance #280
Comments
This is still happening, and the following is how the logs look like currently:
|
@jpkrohling I face this issue when we supply invalid options to jaeger-services.
CR file: (invalid option supplied for jaeger query service) apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: jaegerqe
spec:
strategy: production
query:
replicas: 1
options:
invalidOption: "invalid option"
storage:
type: elasticsearch
elasticsearch:
nodeCount: 1
resources: Operator log:
|
@jkandasa although the underlying problem is similar, the causes are different. This issue should be closed, as the lock was implemented already ("ManagedBy" annotation, IIRC), but we've recently seen the same problem in a different cause during e2e tests (cc @kevinearls). So far, every case where this happened was an edge case, but yours seems more likely to occur in the real world. Could you please open a new issue with your last comment? |
@jpkrohling new issue: #670 |
Currently, it's possible to have two reconciliation iterations concurrently for a given instance. One way to trigger this is executing an
apply
followed by adelete
, like:This is a sample debug log from the operator for the situation above:
(the logs are based on #279)
The text was updated successfully, but these errors were encountered: