failed to store the running status into the current CustomResource

[anarcher]

Describe the bug I deploy fresh install of jaeger operator on K8S and a jaeger deployment but the operator can't reconcile completed.

To Reproduce Steps to reproduce the behavior:

1. deploy fresh install of jaeger operator
2. apply jaeger CRD

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger
  namespace: addon-tracing
spec:
  agent: {}
  allInOne:
    options:
      collector.zipkin.host-port: "9411"
      log-level: debug
      memory.max-traces: 10000
  ingress:
    enabled: false
  sampling:
    options:
      default_strategy:
        param: 0.1
        type: probabilistic
  strategy: allinone

Expected behavior

Reconciling Jaeger completed.

Screenshots If applicable, add screenshots to help explain your problem.

(jaegers.jaegertracing.io \"jaeger\" not found)

Version (please complete the following information):

• k8s: eks 1.18
• Jaeger version: [e.g. 1.8] 1.22.0 (Jaeger Operator: 1.22.1)

What troubleshooting steps did you try? Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.

It seems that the operator can't update the status of Jaeger CRD . Unfortunately, I don't know why (jaegers.jaegertracing.io \"jaeger\" not found)

https://github.com/jaegertracing/jaeger-operator/blob/v1.22.1/pkg/controller/jaeger/jaeger_controller.go#L195

Additional context Add any other context about the problem here.

[jpkrohling]

@rubenvp8510 , could you take a look at this one?

[rubenvp8510]

Sorry I haven't seen this one. I'll take a look in these days to see what could be the issue.

[rafaribe]

I'm experiencing the same problem

[AtkinsChang]

@anarcher If the operator is deployed via helm chart, the CRD is wrong. It does not contains subresource status.

The error message is confusing, it is talking about jaegers.jaegertracing.io/status \"jaeger\" not found. Try yourself with kubernetes API /apis/jaegertracing.io/v1/namespaces/addon-tracing/jaegers/jaeger/status

I would not open PR to fix this because I don't understand the procedure for update jaeger helm chart, I am confusing why the CRD in helm chart is never sync with the operator in git history and there is some pending PRs/Issues related to this matter.