x
/
tobiko
Code Issues Proposed changes

Check all control plane nodes are reponsive after rebooting them 

Some faults tests reboot all the control plane nodes (not only
controllers, but also databases, networkers and messaging nodes as it
was implemented in [1])
After that, tobiko should check the reboot has been finished and the
nodes are responsive, but it only checked the controller nodes

[1] https://review.opendev.org/c/x/tobiko/+/718700

Change-Id: I1e2df2428baf8b44aff3e9048b76809abba314bf
This commit is contained in:
Eduardo Olivares 2022-12-14 15:46:26 +01:00
parent 3bcce0d058
commit 3d874fef9f
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tobiko/tests/faults/ha/cloud_disruptions.py
View File

@ -154,6 +154,9 @@ def reset_all_controller_nodes_sequentially(
def disrupt_all_controller_nodes(disrupt_method=sh.hard_reset_method,
sequentially=False, exclude_list=None):
# TODO(eolivare): join disrupt_all_controller_nodes and
# reboot_all_controller_nodes methods because they are very similar
# reboot all controllers and wait for ssh Up on them
# method : method of disruptino to use : reset | network_disruption
# hard reset is simultaneous while soft is sequential
@ -181,7 +184,7 @@ def disrupt_all_controller_nodes(disrupt_method=sh.hard_reset_method,
if sequentially:
check_overcloud_node_responsive(controller)
if not sequentially:
for controller in topology.list_openstack_nodes(group='controller'):
for controller in nodes:
check_overcloud_node_responsive(controller)
@ -208,7 +211,7 @@ def reboot_all_controller_nodes(reboot_method=sh.hard_reset_method,
controller.name))
tobiko.cleanup_fixture(controller.ssh_client)
if not sequentially:
for controller in topology.list_openstack_nodes(group='controller'):
for controller in nodes:
check_overcloud_node_responsive(controller)