Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Trouble installing the new operator

See original GitHub issue

What happened: I tried installing the new dask operator:

> helm install dask-operator `
>>   dask/dask-kubernetes-operator `
>>   --version 2022.5.2 `
>>   --namespace dask
NAME: dask-operator
LAST DEPLOYED: Fri Jun  3 00:06:44 2022
NAMESPACE: dask
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Operator has been installed successfully.

…which seemed to work

> helm list -n dask
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                                   APP VERSION
dask-operator   dask            1               2022-06-03 00:06:44.6074424 +1000 AEST  deployed        dask-kubernetes-operator-2022.5.2       2022.4.1

But the pod is in ImagePullBackOff:

> kubectl -n dask describe pod/dask-operator-dask-kubernetes-operator-64755dd787-j8qc2
<SNIP>
Containers:
  dask-kubernetes-operator:
    Container ID:
    Image:          ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ErrImagePull
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-4m4cm (ro)
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  3m23s                 default-scheduler  Successfully assigned dask/dask-operator-dask-kubernetes-operator-64755dd787-j8qc2 to aks-compute-23814378-vmss000001
  Normal   Pulling    112s (x4 over 3m23s)  kubelet            Pulling image "ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress"
  Warning  Failed     112s (x4 over 3m22s)  kubelet            Failed to pull image "ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress": rpc error: code = NotFound desc = failed to pull and unpack image "ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress": failed to resolve reference "ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress": ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress: not found
  Warning  Failed     112s (x4 over 3m22s)  kubelet            Error: ErrImagePull
  Warning  Failed     98s (x6 over 3m22s)   kubelet            Error: ImagePullBackOff
  Normal   BackOff    85s (x7 over 3m22s)   kubelet            Back-off pulling image "ghcr.io/dask/dask-kubernetes-operator:set-by-chartpress"

…and seems to be trying to pull a version set-by-chartpress.

i.e. the version appears to not be being set by chartpress!

Environment:

Dask version: latest
Python version: py39
Operating System: linux
Install method (conda, pip, source): conda

Issue Analytics

State:
Created a year ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

jacobtomlinsoncommented, Jun 8, 2022

@consideRatio ah I was setting it to valuesPath: image.tag. My mistake. Many thanks!

1reaction

dhirschfeldcommented, Jun 7, 2022

helm is limited when it comes to upgrading CRDs

Yeah, I’ve come across that before!😬 I wish they’d fix it. https://github.com/helm/community/blob/main/hips/hip-0011.md

Gien that, my plan is to nuke the CRDs whenever I upgrade.

Top Results From Across the Web

Troubleshooting Operator issues - OpenShift Documentation

Operators are a method of packaging, deploying, and managing an OpenShift Container Platform application. They act like an extension of the ...

Troubleshooting OpenShift Container Platform 4.x: Operator ...

Troubleshooting a Hanging Installation Review the status section of each resource for errors or warnings. It's also helpful to look at the logs ......

Operator installation hangs during upgrade - IBM

Resolving the problem · From the navigation pane, click Operators > Installed Operators. · For the operator with Pending status, click the overflow...

Installplan failed because of the error updating CRD #2057

I think when the olm-operator updates the CRD of operator, it failed to match the resourceversion. The User manual workaround is to uninstall ......

Operator 0.9.1 fails to install via Operatorhub on Openshift 4.8 ...

Stand up 4.8 cluster, click buttons in Operatorhub to install Operator, observe error in Operator. Failed Bundle unpacking failed.