-
Notifications
You must be signed in to change notification settings - Fork 40k
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
daemonset handle DeletedFinalStateUnknown #25913
Conversation
Can you confirm that none of the other controllers suffer from the same bug? I don't think they do, I think the keyfunc should handle nil gracefully? |
@bprashanth it looks like the other controllers that define a delete function were accounting for it by using the keyfunc or directly accessing the tombstone when necessary. Below are the items that I found with delete functions:
|
It doesn't check for nil but it does provide a check for the func DeletionHandlingMetaNamespaceKeyFunc(obj interface{}) (string, error) {
if d, ok := obj.(cache.DeletedFinalStateUnknown); ok {
return d.Key, nil
}
return cache.MetaNamespaceKeyFunc(obj)
} |
LGTM |
GCE e2e build/test passed for commit 4d6fee7. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 4d6fee7. |
Automatic merge from submit-queue |
During an e2e run in OpenShift we ran into the DS controller panic when handling
DeletedFinalStateUnknown
. This PR checks forDeletedFinalStateUnknown
and queues the embedded object if it is aDaemonSet
.@mikedanese - would you mind taking a look?
@deads2k
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_check/1002/artifact/origin/artifacts/test-cmd/logs/openshift.log