Skip to content

Conversation

@sdatko
Copy link
Contributor

@sdatko sdatko commented Oct 30, 2025

As part of processing test-operator stages, there is a task that takes all defined Ansible variables and overrides them with matching stage-specific variables. However, this task focuses in the end only on variables specific to test-operator. Yet, because the filtering is done on Ansible task-level, we end up with 80% of the ansible-post-deployment.log filled with entries like skipping <variable_name>. To make this worse, it exposes some deployment-time secrets as a side-effect.

This commit moves the filtering from task-level to earlier phase ~ when the loop arguments are prepared, so we will do override only on the test-operator-related variables, reducing the useless output and avoiding secrets exposure.

@sdatko sdatko requested a review from a team as a code owner October 30, 2025 08:33
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 30, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdatko sdatko force-pushed the test-operator-output branch from 8f8fc0b to 92243f7 Compare October 30, 2025 08:36
@sdatko sdatko changed the title [test-operator] Improve variables overwritting [test-operator] Improve variables overwriting Oct 30, 2025
Copy link
Contributor

@evallesp evallesp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@softwarefactory-project-zuul
Copy link

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/8319138fa8b541b591035f86851ddb43

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 54m 49s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 18m 11s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 24m 26s
✔️ cifmw-multinode-tempest SUCCESS in 1h 36m 03s
✔️ cifmw-pod-zuul-files SUCCESS in 4m 33s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 28m 11s
cifmw-pod-pre-commit FAILURE in 6m 34s
✔️ build-push-container-cifmw-client SUCCESS in 17m 06s
✔️ cifmw-molecule-test_operator SUCCESS in 3m 53s

@sdatko sdatko enabled auto-merge (rebase) October 30, 2025 14:04
As part of processing test-operator stages, there is a task
that takes all defined Ansible variables and overrides them
with matching stage-specific variables. However, this task
focuses in the end only on variables specific to test-operator.
Yet, because the filtering is done on Ansible task-level,
we end up with 80% of the `ansible-post-deployment.log`
filled with entries like `skipping <variable_name>`.
To make this worse, it exposes some deployment-time secrets
as a side-effect.

This commit moves the filtering from task-level to earlier
phase ~ when the loop arguments are prepared, so we will
do override only on the test-operator-related variables,
reducing the useless output and avoiding secrets exposure.
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.

2 participants