Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
Description
When I had issues with provisioning due to some misconfigured networks, I ran the 05_host_cleanup.sh script but it didn't fully clean up everything. If I ran "kubectl get bmh -A" I still had my two vm's stuck in the "provisioning" stage. That resource never got deleted so when I tried to setup the vm's again with the following scripts it failed.
01_install_requirements.sh
02_configure_host.sh
03_launch_mgmt_cluster.sh
I had to manually delete the bmh resource "kubectl delete bmh -n metal3 master-0" and also "kubectl delete -bmh -n metal3 worker-0"