Description of problem: Jul 3 14:56:48.228: INFO: Couldn't delete ns: "svcaccounts-5720": namespace svcaccounts-5720 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace svcaccounts-5720 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"}) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://prow.k8s.io/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/1525 https://prow.k8s.io/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/1532
Saw similar log: Jul 26 12:02:12.799: INFO: Couldn't delete ns: "e2e-svcaccounts-2097": namespace e2e-svcaccounts-2097 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace e2e-svcaccounts-2097 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"}) https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/2512#0:build-log.txt%3A18770
I think this is slow pod deletion and we backoff when we shouldn't (I have a PR upstream to fix that). Mike, can you check the logs to see if there is a pod that took too long to delete and send it to Node team to find out why?
Is this a dup of bug 1713135?
To me this looks more like dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1727090, I'm closing this in favour of the other one, since there's already an investigation happening. *** This bug has been marked as a duplicate of bug 1727090 ***