-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What's the expected behavior for rescued tasks in a *finalizer*? #88
Comments
@markuszoeller: The label(s) In response to this:
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-sigs/prow repository. |
Type of question
How to implement a specific feature
Question
What did you do?
I've implemented a finalizer for my CRD and some tasks in there are in a rescue block and if rescued, the custom resource does NOT get deleted, but the delete is tried forever while there's an error at the end of the finalizer playbook run:
What did you expect to see?
The tasks in the finalizer that got rescued do not block the deletion of the custom resource
What did you see instead? Under which circumstances?
The tasks in the finalizer that got rescued DO block the deletion of the custom resource and it gets reconciled over and over.
Environment
Operator type:
language ansible
Kubernetes cluster type:
OpenShift
$ operator-sdk version
$ go version
(if language is Go)$ kubectl version
Additional context
Considering rescue block seems to have been introduced with https://github.com/operator-framework/operator-sdk/pull/3650/files but I'm wondering if that also applies to finalizers.
The text was updated successfully, but these errors were encountered: