Enable running the test-operator role multiple times #2412
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Thanks for the PR! ❤️ |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/de081b8b9823412e9114978d4382adbb ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 28m 42s |
lpiwowar
force-pushed
the
bugfix/multiple-test-operator-runs
branch
from
4bc0d24
to
8ca52e7
Compare
It was not possible to run the test-operator role multiple times without cleaning up all resources created by the first run, such as the logs pod created for the logs collection. This patch makes it possible to run the test operator role multiple times without cleaning up the resources (e.g., after the update in an update job). It is possible because: - test-operator-logs pod now has unique name for each job run - The variable cifmw_test_operator_*_name is now exposed. By specifying a unique name, we can guarantee no name collisions between the test-operator related resources (logs pods, instances of CRs) If you want to run test-operator role twice within a single job then make sure that for the second run you specify a value for the cifmw_test_operator_*_name. For example: cifmw_test_operator_tempest_name: "post-update-tempest-tests"
lpiwowar
force-pushed
the
bugfix/multiple-test-operator-runs
branch
from
8ca52e7
to
c33ee46
Compare
It was not possible to run the test-operator role multiple times without cleaning up all resources created by the first role run, such as the logs pod created for the logs collection.
This patch makes it possible to run the test operator role multiple times without cleaning up the resources (e.g., after the update in an update job). It is possible because:
If you want to run test-operator role twice within a single job then make sure that for the second run you specify a value for the cifmw_test_operator_*_name. For example:
cifmw_test_operator_tempest_name: "post-update-tempest-tests"