From 8d82cbe0d62a16b547e42a1d1b83054426b543c3 Mon Sep 17 00:00:00 2001 From: Waldemar Znoinski Date: Tue, 19 Apr 2016 16:16:10 +0100 Subject: [PATCH] add waiter for server to become ACTIVE after reboot There looks to be a race condition between server reboot request and cleanup fuction that runs when the test finishes. This change add explicit waiting for server to be back to 'ACTIVE' state after being rebooted. Change-Id: I990977e02bd09e59b52ab72cb461aa720b8e2052 Closes-Bug: #1572197 --- intel_nfv_ci_tests/tests/scenario/test_cpu_pinning.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/intel_nfv_ci_tests/tests/scenario/test_cpu_pinning.py b/intel_nfv_ci_tests/tests/scenario/test_cpu_pinning.py index 267f4c1..63df4d8 100644 --- a/intel_nfv_ci_tests/tests/scenario/test_cpu_pinning.py +++ b/intel_nfv_ci_tests/tests/scenario/test_cpu_pinning.py @@ -156,7 +156,8 @@ class CPUPolicyTest(base.BaseV2ComputeAdminTest): def _reboot_server(self, server, reboot_type): self.servers_client.reboot_server(server['id'], type=reboot_type) - + waiters.wait_for_server_status(self.servers_client, + server['id'], 'ACTIVE') # get more information server = self.servers_client.show_server(server['id'])['server']