Ensure server unlocking after test_lock_unlock_server
If assertRaises() in test_lock_unlock_server fails for some
reason, the server remains in locked state and cannot be
deleted after execution of test cases.
addCleanup call for server unlocking is added so that in case
of test_lock_unlock_server failure there will be no hanging
servers in the system after tempest run.
Change-Id: Iff336723d8e03814d9361492b1d5856b785f7a4c
Closes-Bug: #1468623
diff --git a/tempest/api/compute/servers/test_server_actions.py b/tempest/api/compute/servers/test_server_actions.py
index f0f6b8c..234f7e1 100644
--- a/tempest/api/compute/servers/test_server_actions.py
+++ b/tempest/api/compute/servers/test_server_actions.py
@@ -474,6 +474,7 @@
def test_lock_unlock_server(self):
# Lock the server,try server stop(exceptions throw),unlock it and retry
self.client.lock_server(self.server_id)
+ self.addCleanup(self.client.unlock_server, self.server_id)
server = self.client.show_server(self.server_id)
self.assertEqual(server['status'], 'ACTIVE')
# Locked server is not allowed to be stopped by non-admin user