We recently encountered a timeout issue during the deletion of the test-operator, as shown below:
2024-09-01 09:48:16,114 p=26025 u=zuul n=ansible | TASK [test_operator : Delete Operator kubeconfig=\{{ cifmw_openshift_kubeconfig }}, api_key=\{{ cifmw_openshift_token | default(omit)}}, context=\{{ cifmw_openshift_context | default(omit)}}, kind=Operator, state=absent, api_version=operators.coreos.com/v1, name=test-operator.openstack, namespace=\{{ cifmw_test_operator_namespace }}, wait=True] ***
2024-09-01 09:48:16,114 p=26025 u=zuul n=ansible | Sunday 01 September 2024 09:48:16 -0400 (0:00:06.707) 5:32:48.928 ******
2024-09-01 09:50:18,459 p=26025 u=zuul n=ansible | fatal: [localhost]: FAILED! => changed=true
duration: 120
method: delete
msg: '"Operator" "test-operator.openstack": Timed out waiting on resource'

The default timeout is set to 120 seconds. By adding the `wait_timeout` parameter to the cleanup tasks [1], we can extend this time frame.

DoD:

• The tasks in the cleanup.yml in the test-operator role have wait_timeout parameter configurable through role variable.

[1] https://github.com/openstack-k8s-operators/ci-framework/blob/3f5725020468ce17a1b27908faff20745cfe6870/roles/test_operator/tasks/cleanup.yml

PR:

• https://github.com/openstack-k8s-operators/ci-framework/pull/2305
• https://github.com/openstack-k8s-operators/ci-framework/pull/2346