Charts: [stable/jaeger-operator] Chart installation fails with crd already exists

Created on 21 Dec 2018  路  6Comments  路  Source: helm/charts

Is this a request for help?:

No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:
kubernetes 1.11.5
helm 2.12.0

Which chart:
stable/jaeger-operator

What happened:

  • run helm install --name jaeger-operator --namespace tracing stable/jaeger-operator
  • installation fails with following error
    ~
    Error: release jaeger-operator failed: customresourcedefinitions.apiextensions.k8s.io "jaegers.io.jaegertracing" already exists
    ~

What you expected to happen:
Installation should complete successfully.

How to reproduce it (as minimally and precisely as possible):

  • run helm install --name jaeger-operator --namespace tracing stable/jaeger-operator

Anything else we need to know:
Proabably crd.yaml needs some conditionals such as https://github.com/helm/charts/blob/master/stable/prometheus-operator/templates/prometheus-operator/crd-prometheusrules.yaml#L1

Most helpful comment

I notice the same issue with Helm 2.14.0.

All 6 comments

I was able to work around this by adding flag --no-crd-hook to the helm install command

sounds good, i will add that in the chart

@cpanato No need to. I think this is a helm 2.12.0 issue. I tested the chart on another cluster with helm 2.11.0 and the chart got installed without any issues.

Found a new helm release which should fix this, https://github.com/helm/helm/releases/tag/v2.12.1

testing it now

Upgrade to 2.12.1 works. I'm closing this issue.

I notice the same issue with Helm 2.14.0.

Was this page helpful?
0 / 5 - 0 ratings