Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Done
-
Casablanca Release
-
None
Description
do a force delete as a workaround
example on
https://git.onap.org/logging-analytics/tree/deploy/cd.sh#n74
ubuntu@ip-172-31-1-119:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-6cfb49f776-wp2pr 1/1 Running 0 3d kube-system kube-dns-75c8cb4ccb-6xllj 3/3 Running 35 4d kube-system kubernetes-dashboard-6f4c8b9cd5-bx4jw 1/1 Running 0 4d kube-system monitoring-grafana-76f5b489d5-xnkc2 1/1 Running 0 6d kube-system monitoring-influxdb-6fc88bd58d-mbvk5 1/1 Running 0 13d kube-system tiller-deploy-6ffff75db6-mqgvb 1/1 Running 0 5d onap onap-portal-db-config-h75lt 0/2 Terminating 0 2d
results
ubuntu@ip-172-31-1-119:~$ kubectl delete pod onap-portal-db-config-h75lt -n onap --grace-period=0 --force warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "onap-portal-db-config-h75lt" deleted ubuntu@ip-172-31-1-119:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-6cfb49f776-wp2pr 1/1 Running 0 3d kube-system kube-dns-75c8cb4ccb-6xllj 3/3 Running 35 4d kube-system kubernetes-dashboard-6f4c8b9cd5-bx4jw 1/1 Running 0 4d kube-system monitoring-grafana-76f5b489d5-xnkc2 1/1 Running 0 6d kube-system monitoring-influxdb-6fc88bd58d-mbvk5 1/1 Running 0 13d kube-system tiller-deploy-6ffff75db6-mqgvb 1/1 Running 0 5d