[ICN-528] The 05_host_cleanup.sh doesn't remove the bmh crd causing problems on subsequent runs Created: 27/Jan/21 Updated: 27/Aug/21 |
|
| Status: | To Do |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Eric Adams | Assignee: | Kuralamudhan Ramakrishnan |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 I had to manually delete the bmh resource "kubectl delete |
| Comments |
| Comment by Geoffroy Van Cutsem [ 27/Aug/21 ] |
|
For what it's worth, the script you mention is run with the top-level 'make bmh_clean_host'. Deleting these CRDs should be done if you run 'make bmh_clean' (during the './01_metal3.sh deprovision' step [in 'deploy/metal3/scripts/').
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? |