This repository has been archived by the owner on Nov 17, 2021. It is now read-only.

Garbage collecting a CRD causes spurious "not found" error #250

Open

anguslees opened this issue May 3, 2019 · 0 comments

Labels

bug

Contributor

anguslees commented May 3, 2019

I decided to remove my Argo install, and hit this:

...
INFO  Garbage collecting clusterroles argo-ui-cluster-role (rbac.authorization.k8s.io/v1beta1)
INFO  Garbage collecting customresourcedefinitions workflows.argoproj.io (apiextensions.k8s.io/v1beta1)
ERROR the server could not find the requested resource (get workflows.argoproj.io)

(The CRD was deleted, and then gc tried to fetch instances of that custom resource)

kubecfg should ignore all variants of "not found" when walking the resources for garbage collection.

The text was updated successfully, but these errors were encountered:

anguslees added the bug label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.