-
Bug
-
Resolution: Done
-
Medium
-
Amsterdam Release
-
None
-
None
A change was put in to auto delete onap-config on any type of delete - which is OK because the one-time container is stopped
However the deleteAll script should not report a failure on a missing config pod the 2nd time it gets run
ubuntu@ip-172-31-52-161:~/oom/kubernetes/oneclick$ ./deleteAll.bash -n onap -a logdemo 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-logdemo" deleted namespace "onap-logdemo" deleted clusterrolebinding "onap-logdemo-admin-binding" deleted Service account onap-logdemo-admin-binding deleted. Error: release: "onap-config" not found namespace "onap" deleted Waiting for namespaces termination... ********** Gone **********