-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
We should not be removing the config container unless specified - or maybe when removing everything
has no effect on the existing config - the container is already 0/1 - a one time config
root@ip-172-31-4-19:~/oom/kubernetes/oneclick# kubectl get pods --all-namespaces | grep 0/ onap-aaf aaf-c68d8877c-vxhbc 0/1 Running 0 39m onap-consul consul-agent-5c744c8758-lmgt5 0/1 CrashLoopBackOff 11 39m onap-consul consul-server-687f6f6556-2q4kt 0/1 CrashLoopBackOff 11 39m onap-consul consul-server-687f6f6556-f7kqn 0/1 CrashLoopBackOff 10 39m onap-vfc vfc-ztevnfmdriver-585d8db4f7-l8vq6 0/1 ImagePullBackOff 0 39m root@ip-172-31-4-19:~/oom/kubernetes/oneclick# ./deleteAll.bash -n onap -a consul Current kubectl context does not match context specified: onap You are about to delete deployment from: onap To continue enter context name: onap ********** Cleaning up ONAP: release "onap-consul" deleted namespace "onap-consul" deleted clusterrolebinding "onap-consul-admin-binding" deleted Service account onap-consul-admin-binding deleted. Error: release: "onap-config" not found namespace "onap" deleted Waiting for namespaces termination... ********** Gone **********