🐛 Move ahead with cluster deletion if current resource in sequence is not found
snehala27 opened this issue · 6 comments
/kind bug
What steps did you take and what happened:
Create a GCP cluster.
In case of unusual cluster deletion(like partial cluster creation took place or partial deletion happened in the previous run), the resources get deleted in a sequence. If the resource to be deleted in sequence is not found, then the deletion process gets stuck with error specifying resource not found.
What did you expect to happen:
In such cases, if the resource does not exist, the deletion process should move ahead with the next resource in sequence.
Anything else you would like to add:
Environment:
- Cluster-api version:
- Minikube/KIND version:
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):
/assign
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
@cpanato: Closing this issue.
In response to this:
fixed here: #347
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.