https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/ICN-528 Integrated Cloud Native NFV <p>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.</p> <p>01_install_requirements.sh<br/> 02_configure_host.sh<br/> 03_launch_mgmt_cluster.sh</p> <p>I had to manually delete the bmh resource "kubectl delete <del>bmh -n metal3 master</del>-0" and also "kubectl delete -bmh -n metal3 worker-0"</p> ICN-528

The 05_host_cleanup.sh doesn't remove the bmh crd causing problems on subsequent runs

Bug Medium To Do Unresolved Kuralamudhan Ramakrishnan Eric Adams Wed, 27 Jan 2021 19:40:52 +0000 Fri, 27 Aug 2021 13:30:10 +0000 0 2 <p>For what it's worth, the script you mention is run with the top-level 'make bmh_clean_host'.</p> <p>Deleting these CRDs should be done if you run 'make bmh_clean' (during the './01_metal3.sh deprovision' step [in 'deploy/metal3/scripts/').</p> <p> </p> <p>I'm not quite sure what the difference is supposed to be between 'make bmh_clean_host' and 'make bmh_clean'. Perhaps it is by design that such resources are only deleted in the 'bmh_clean' target?</p> Development Rank 0|i00550: