Code Review / releng-xci.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: c7ceaa7) | patch
prototypes: bifrost: destroy-env: Always destroy XCI VMs 53/39153/2
authorMarkos Chandras <mchandras@suse.de>
Wed, 26 Jul 2017 10:25:22 +0000 (11:25 +0100)
committerMarkos Chandras <mchandras@suse.de>
Thu, 17 Aug 2017 13:48:06 +0000 (13:48 +0000)
commit5b0410aa4f51e50df6b171cf8592a7bfaa6de796
treef132c92dd4feab8ee2152e2461e76b95abb24563tree | snapshot
parentc7ceaa77fba0d3dbe0ca802d0b4c159f38b6cbf9commit | diff
prototypes: bifrost: destroy-env: Always destroy XCI VMs

It's possible that a previous run failed before registering the VMs
to the vbmc. As such, consulting the vbmc to retrieve the VM names will
return nothing and no VM will be deleted. As such, it's best to get
the VMs from the currently XCI profile and make sure they are really
gone.

Change-Id: If11265655f42c8a1c7627c9139ac0cbfc002b1fe
Signed-off-by: Markos Chandras <mchandras@suse.de>
bifrost/scripts/destroy-env.sh diff | blob | history