From 85c5ec11c9526e0429163db5701d3ea8c096a324 Mon Sep 17 00:00:00 2001 From: Akihiro Motoki Date: Wed, 15 Jan 2020 10:58:29 +0900 Subject: [PATCH] Cleanup VM instances during unstack Currently VMs created by a previous DevStack run still exists even after re-run stack.sh. This leads to a failure in launching a VM after the second run of stack.sh. We need to check the reason of the failure by nova compute log and clean up remaining VMs. It is annoying. IIRC we cleaned up existing VMs. While I failed to identify which commit changed this behavior, I believe it is worth recovering it. This commit changes unstack.sh to call cleanup_nova. cleanup_cinder() already cleans up LVM volumes and some of them may be used by VMs, so I believe it is reasonable to clean up VMs in unstack.sh. Change-Id: I9fcbc5105e443037fada1ef6a76a078145964256 --- unstack.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/unstack.sh b/unstack.sh index ccea0ef585..276111edb9 100755 --- a/unstack.sh +++ b/unstack.sh @@ -99,6 +99,7 @@ run_phase unstack if is_service_enabled nova; then stop_nova + cleanup_nova fi if is_service_enabled placement; then