From 1833f3e2fc192c03ed04431cdfefb9dac2aca355 Mon Sep 17 00:00:00 2001 From: Eduardo Olivares Date: Wed, 29 Nov 2023 15:33:09 +0100 Subject: [PATCH] Increase retry timeout to obtain multi_ip_test_fixture.vms_detailed_info Test test_z99_reboot_controller_galera_main_vip creates a set of 10 VMs. While the creation is in progress, the test reboots some controller nodes. Then, it waits until all VMs are created. It uses a timeout because sometimes not all the VMs reach the ACTIVE status due to the controller rebooted. The timeout value of 4 minutes seems to be not enough in some cases. This patch increases that value to 5 minutes. Change-Id: I40fa9798f71d82047237e914373016122f54a392 --- tobiko/tests/faults/ha/cloud_disruptions.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tobiko/tests/faults/ha/cloud_disruptions.py b/tobiko/tests/faults/ha/cloud_disruptions.py index 9e70b5285..1f6025893 100644 --- a/tobiko/tests/faults/ha/cloud_disruptions.py +++ b/tobiko/tests/faults/ha/cloud_disruptions.py @@ -369,7 +369,7 @@ def disrupt_controller_galera_main_vip(disrupt_method=sh.soft_reset_method): def get_vms_detailed_info(multi_ip_test_fixture): - for attempt in tobiko.retry(timeout=240, interval=10): + for attempt in tobiko.retry(timeout=300, interval=10): # dynamically obtain the status of the VMs vms_detailed_info = multi_ip_test_fixture.vms_detailed_info