-
Bug
-
Resolution: Done
-
Medium
-
Casablanca Release
-
None
example - using cd.sh
We are stuck at the following line
https://git.onap.org/logging-analytics/tree/deploy/cd.sh#n95
sudo helm undeploy $ENVIRON --purge
before we can get to the loop that would purge the node
https://git.onap.org/logging-analytics/tree/deploy/cd.sh#n122
export POD_NAMES=$(kubectl get pods --field-selector=status.phase!=Running --all-namespaces -o jsonpath="
")
echo "--force delete on pods: $POD_NAMES"
for pod in $POD_NAMES; do
echo "running: kubectl delete pods $pod --grace-period=0 --force -n $ENVIRON"
kubectl delete pods $pod --grace-period=0 --force -n $ENVIRON
ubuntu@a-cd-cas0:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-7b48b696fc-j4x45 1/1 Running 0 15d kube-system kube-dns-6655f78c68-zdxsd 3/3 Running 3 15d kube-system kubernetes-dashboard-6f54f7c4b-7kpwf 1/1 Running 0 15d kube-system monitoring-grafana-7877679464-f8j56 1/1 Running 0 15d kube-system monitoring-influxdb-64664c6cf5-5hqnt 1/1 Running 0 15d kube-system tiller-deploy-6f4745cbcf-cdmzl 1/1 Running 0 15d onap onap-oof-oof-has-reservation-5cd655b79f-56cn7 0/1 Terminating 0 15d (+) will try moving the helm undeploy after the force deletes
- blocks
-
TSC-25 Task Force to implement CD (Continuous Deployment)
- Closed
- is blocked by
-
LOG-898 ONAP Deployment Resiliency changes to deploy without POD failures
- Closed
-
LOG-326 CD: OOM automated deployment script
- Closed
-
LOG-925 Adjust deployment dependency list - msb must be before dcaegen2
- Closed
- relates to
-
OOM-1586 Add --force --grace-period=0 delete pod capability to cd.sh script
- Closed
-
OOM-1089 DCAE pods are not getting purged
- Closed