Skip to content

[DNM] parallel_group support test#3844

Draft
Valkyrie00 wants to merge 3 commits intoopenstack-k8s-operators:mainfrom
Valkyrie00:feat/test-operator-parallel-stages
Draft

[DNM] parallel_group support test#3844
Valkyrie00 wants to merge 3 commits intoopenstack-k8s-operators:mainfrom
Valkyrie00:feat/test-operator-parallel-stages

Conversation

@Valkyrie00
Copy link
Copy Markdown
Contributor

WIP

…t stages

Stages sharing the same parallel_group value are applied simultaneously
as independent Tempest CRs, leveraging the test-operator's inter-CR
parallelism. The first CR creates shared resources (images, flavors)
with a configurable pause before remaining CRs start, preventing
race conditions.

New files:
- load-stage-vars.yml: extracted stage var loading (shared by both paths)
- dispatch-stage.yml: routes stages to sequential or parallel execution
- parallel_stages.yml: orchestrates parallel group lifecycle
- build-parallel-cr.yml: builds a single CR reusing tempest-tests.yml
- collect-parallel-logs.yml: collects logs from parallel CR PVCs
- cleanup-parallel.yml: cleans up parallel CRs and log pods

New defaults:
- cifmw_test_operator_parallel_resource_wait (120s)
- cifmw_test_operator_parallel_timeout (14400s)
- cifmw_test_operator_parallel_resources (500m/512Mi req, 2cpu/2Gi limit)

Backward compatible: stages without parallel_group work exactly as before.

Made-with: Cursor
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 12, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dasm for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@softwarefactory-project-zuul
Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/840f992f4ab24aa2b52765562a25ec6a

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 20m 57s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 21m 36s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 30m 40s
✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 2h 08m 08s
✔️ cifmw-multinode-tempest SUCCESS in 1h 52m 23s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 46s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 53s
cifmw-pod-pre-commit FAILURE in 8m 23s
✔️ cifmw-molecule-test_operator SUCCESS in 3m 07s

The base scenario's tempest workflow (multi-thread/single-thread steps)
was being inherited by each parallel CR, causing all CRs to run the
full test suite instead of their intended subset. Each parallel stage
defines its own tests via top-level includeList/excludeList, so the
workflow must be empty.

Made-with: Cursor
@softwarefactory-project-zuul
Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7b6c857be59343f1a69b99af5a45d657

✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 46m 43s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 30m 07s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 32m 11s
✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 2h 09m 07s
✔️ cifmw-multinode-tempest SUCCESS in 1h 50m 43s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 58s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 48s
cifmw-pod-pre-commit FAILURE in 9m 22s
✔️ cifmw-molecule-test_operator SUCCESS in 3m 15s

Log pods (busybox with sleep infinity) were left Running after copying
logs from PVCs. Now each log pod is deleted immediately after its logs
are copied and HTML reports generated.

Made-with: Cursor
@softwarefactory-project-zuul
Copy link
Copy Markdown

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/eaa0748a2a1a41be90eea1c21696520c

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 26m 22s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 25m 04s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 44m 43s
✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 2h 07m 23s
✔️ cifmw-multinode-tempest SUCCESS in 1h 59m 01s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 49s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 18s
cifmw-pod-pre-commit FAILURE in 8m 28s
✔️ cifmw-molecule-test_operator SUCCESS in 3m 09s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant