Pop VM from list after deleting it

now that we are checking nova commands for proper return
codes, we cannot just happily delete things that are already
deleted. So, for the test case where we delete a single
instance to make sure ping traffic fails, we also need to
remove that instance from the list and let further cleanup
skip it.

Change-Id: Id0578e2c187e4b6703f76a11e369ffb92f6e17af
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>

diff --git a/csit/suites/openstack/connectivity/l2.robot b/csit/suites/openstack/connectivity/l2.robot
index 6e47d7a9b3929444c4b6b3070992c004c4843b9c..8111e0b07704a09d8eda7015fed882bc9dff3b32 100644 (file)
--- a/csit/suites/openstack/connectivity/l2.robot
+++ b/csit/suites/openstack/connectivity/l2.robot
@@ -122,8 +122,10 @@ Connectivity Tests From Vm Instance3 In net_2
     OpenStackOperations.Test Operations From Vm Instance    @{NETWORKS}[1]    @{NET_2_VM_IPS}[2]    ${NET_2_VM_IPS}
 
 Delete A Vm Instance
-    [Documentation]    Delete Vm instances using instance names.
+    [Documentation]    Delete Vm instances using instance names. Also remove the VM from the
+    ...    list so that later cleanup will not try to delete it.
     OpenStackOperations.Delete Vm Instance    @{NET_1_VMS}[0]
+    Remove From List    ${NET_1_VMS}    0
 
 No Ping For Deleted Vm
     [Documentation]    Check non reachability of deleted vm instances by pinging to them.