USHIFT-7457: bump sonobuoy version to v0.57.5

[eslutsky]

Summary by CodeRabbit

• Chores
  • Updated the bundled Sonobuoy version from v0.57.3 to v0.57.5.
  • Updated the bundled GitOps version from 1.19 to 1.21.
  • Updated release validation to use the latest OpenShift mirror sources for previous releases.
  • Standardized version references across validation and tooling workflows, ensuring releases use the latest configured component versions consistently.

[openshift-ci-robot]

@eslutsky: This pull request references USHIFT-6396 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: a2907f5d-1a91-4b9a-87f4-343eb382869c

📥 Commits

Reviewing files that changed from the base of the PR and between 80984f7 and 72888d8.

📒 Files selected for processing (1)

• test/bin/common_versions.sh

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

Shared test configuration now resolves previous and y-2 releases from OpenShift mirror URLs. It also updates Sonobuoy to v0.57.5 and MicroShift GitOps to 1.21.

Changes

Test configuration

Layer / File(s)	Summary
Release repository resolution test/bin/common_versions.sh	Previous and y-2 release repositories now use OpenShift mirror URLs. Their version lookups now call get_vrel_from_beta. Previous-release major and minor variables are empty.
Test tool versions test/bin/common_versions.sh, test/bin/pyutils/generate_common_versions.py	Sonobuoy changes to v0.57.5 in both definitions. MicroShift GitOps changes to 1.21. The systemd-logs version remains v0.4.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 72888

This localized test-tooling version update introduces no actionable merge-blocking risk and is merge-ready after normal checks and review.

Suggested labels: ready-for-human-review

Suggested reviewers: ggiguash, jogeo, agullon

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change: updating Sonobuoy to v0.57.5.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The diff changes only release/version variables in test/bin/common_versions.sh; it adds no Ginkgo test titles or dynamic test-name content.
Test Structure And Quality	✅ Passed	The PR diff changes only version-resolution shell/Python files; it adds or modifies no Ginkgo It blocks, setup/cleanup, waits, or assertions covered by this check.
Microshift Test Compatibility	✅ Passed	The PR diff changes only test/bin/common_versions.sh and adds no Ginkgo tests or OpenShift API references requiring MicroShift compatibility checks.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The commit changes only test/bin/common_versions.sh version and repository variables; it adds no Ginkgo e2e tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit modifies only test/bin/common_versions.sh version and repository variables; it adds no manifests, operators, controllers, or scheduling constraints covered by this check.
Ote Binary Stdout Contract	✅ Passed	The commit changes only test/bin/common_versions.sh version variables and repository resolution; it adds no OTE binary process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only version and repository variables in two shell/Python files; it adds no Ginkgo e2e tests or test networking code.
No-Weak-Crypto	✅ Passed	The diff changes repository URLs, release variables, and Sonobuoy/GitOps versions only; no added MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons appear.
Container-Privileges	✅ Passed	The PR changes only version-resolution shell/Python files; the diff adds no container or Kubernetes manifest privilege settings.
No-Sensitive-Data-In-Logs	✅ Passed	The commit changes only repository URLs, release flags, and version values; it adds no logging or output statements, and the URLs are public mirror.openshift.com paths.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [eslutsky]

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

[openshift-ci-robot]

@eslutsky: This pull request references USHIFT-7457 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

• Chores
• Updated the bundled Sonobuoy version from v0.57.3 to v0.57.5.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[pacevedom]

/retest

[openshift-ci]

@eslutsky: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-tests-bootc-periodic-arm-el10	72888d8	link	true	/test e2e-aws-tests-bootc-periodic-arm-el10
ci/prow/e2e-aws-tests-periodic	72888d8	link	true	/test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests-bootc-arm-el10	72888d8	link	true	/test e2e-aws-tests-bootc-arm-el10
ci/prow/e2e-aws-tests-bootc-arm-el9	72888d8	link	true	/test e2e-aws-tests-bootc-arm-el9
ci/prow/e2e-aws-tests-bootc-el9	72888d8	link	true	/test e2e-aws-tests-bootc-el9
ci/prow/e2e-aws-tests	72888d8	link	true	/test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc-el10	72888d8	link	true	/test e2e-aws-tests-bootc-el10
ci/prow/e2e-aws-tests-periodic-arm	72888d8	link	true	/test e2e-aws-tests-periodic-arm
ci/prow/e2e-aws-tests-bootc-periodic-el10	72888d8	link	true	/test e2e-aws-tests-bootc-periodic-el10
ci/prow/e2e-aws-tests-bootc-periodic-el9	72888d8	link	true	/test e2e-aws-tests-bootc-periodic-el9
ci/prow/e2e-aws-tests-bootc-periodic-arm-el9	72888d8	link	true	/test e2e-aws-tests-bootc-periodic-arm-el9
ci/prow/e2e-aws-tests-arm	72888d8	link	true	/test e2e-aws-tests-arm

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.