starlingx
/
test
Code Issues Proposed changes

Fix the case when a test trying to reboot active controller fails because stx-openstack is not applied 

Description: The test_reboot_active_controller fails because the stx-openstack is not applied:
...RegionOne host-swact controller-1' failed to execute. Output: Swact action not allowed. stx-openstack apply is in progress.
During reboot of the active controller a swact should be performed which fails.

Story: N/A
Task: N/A

Signed-off-by: Alexandru <alexandru.dimofte@intel.com>
Change-Id: I363a8328159d5ce086e05037997f7f3bdd197207
This commit is contained in:
Alexandru 2022-01-12 15:37:42 +02:00
parent e1a904f6b3
commit aeb2e87a20
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
automated-pytest-suite/testcases/sanity/sanity_openstack/test_host_management.py
View File

@ -195,6 +195,8 @@ def test_reboot_active_controller(no_simplex):
availability=['available'])
kube_helper.wait_for_pods_healthy(check_interval=30,
all_namespaces=True)
container_helper.wait_for_apps_status(apps="stx-openstack", status=AppStatus.APPLIED,
timeout=600, check_interval=60)
host_helper.swact_host(hostname=standby)