Description of problem:
Customer found two pods in 'unknown' and 'terminating' state. Tried deleting with oc delete but pods remained.
Nodes that hosted these pods were evacuated and deleted from the cluster with 'oc delete node <node-name>' and 'usr/share/ansible/openshift-ansible/playbooks/adhoc/uninstall.yml' playbook was run afterwards.
The two pods in terminating and unknown state still appeared in output of oc get pods.
Tried 'oc delete pods <pod_name> --grace-period=0 --force' but pods still listed in oc get pods command as terminating and unknown (see attached screenshot).
In the output of 'oc delete pods <pod_name> --grace-period=0 --force --loglevel=8', the following failure message appears:
'"status":{"phase":"Failed","message":"Node oscp-node1.redacted.com which was running pod keycloak-27-deploy is unresponsive","reason":"NodeLost","startTime":"2018-02-19T19:15:25Z"}}'
Version-Release number of selected component (if applicable):
3.7
How reproducible:
Delete nodes that pods in 'terminating' or 'unknown' state reside on and then try to delete those pods.
Actual results:
Pods not deleted.
Expected results:
Pods deleted.
Additional info:
Attachments in separate comment.
We had similar problem in 3.6 and used this command to get rid of unruly pods
oc delete po/$pod -n $namespace --grace-period=0 --force=true --ignore-not-found=true
OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed.
[1]: https://access.redhat.com/support/policy/updates/openshift
Description of problem: Customer found two pods in 'unknown' and 'terminating' state. Tried deleting with oc delete but pods remained. Nodes that hosted these pods were evacuated and deleted from the cluster with 'oc delete node <node-name>' and 'usr/share/ansible/openshift-ansible/playbooks/adhoc/uninstall.yml' playbook was run afterwards. The two pods in terminating and unknown state still appeared in output of oc get pods. Tried 'oc delete pods <pod_name> --grace-period=0 --force' but pods still listed in oc get pods command as terminating and unknown (see attached screenshot). In the output of 'oc delete pods <pod_name> --grace-period=0 --force --loglevel=8', the following failure message appears: '"status":{"phase":"Failed","message":"Node oscp-node1.redacted.com which was running pod keycloak-27-deploy is unresponsive","reason":"NodeLost","startTime":"2018-02-19T19:15:25Z"}}' Version-Release number of selected component (if applicable): 3.7 How reproducible: Delete nodes that pods in 'terminating' or 'unknown' state reside on and then try to delete those pods. Actual results: Pods not deleted. Expected results: Pods deleted. Additional info: Attachments in separate comment.