USHIFT-7113: Update openshift-test-private commit to recent

[kasturinarra]

Summary by CodeRabbit

• Chores
  • Updated test infrastructure configuration versions.

[coderabbitai]

Walkthrough

Updates the test private repository commit pin from b5111e366dc8f517732c6d48219ed659497de8e0 to 7f4370e1e2d03b56b1f858ec10a84ea12375196d in both the template and generated version script files.

Changes

Test private repository commit pin update

Layer / File(s)	Summary
Test private repository commit pin test/assets/common_versions.sh.template, test/bin/common_versions.sh	Both files update OPENSHIFT_TESTS_PRIVATE_REPO_COMMIT to the new commit hash. Template and script remain synchronized.

---

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

ready-for-human-review

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 PR changes only shell scripts that export version variables; no Ginkgo test files are modified. The check for "Stable and Deterministic Test Names" does not apply.
Test Structure And Quality	✅ Passed	PR only modifies shell scripts (common_versions.sh files) that set environment variables; no Ginkgo test code present, making the check inapplicable.
Microshift Test Compatibility	✅ Passed	PR only updates version commit hashes in shell script configuration files; no new Ginkgo tests are added to this repository that would require MicroShift compatibility checks.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR updates only shell script configuration files (test/bin/common_versions.sh and template), not Ginkgo e2e tests. Custom check applies only to new test additions.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates commit hash in test config files; no deployment manifests, operator code, controllers, or scheduling constraints are added or modified.
Ote Binary Stdout Contract	✅ Passed	PR only updates shell script version configuration files, not OTE binary code; check applies only to process-level stdout writes in binaries.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only updates commit hash in shell script configuration files; no new Ginkgo e2e tests are added, making the IPv6/disconnected network test check not applicable.
No-Weak-Crypto	✅ Passed	PR only updates commit hash values in configuration files. No weak crypto, custom crypto implementations, or insecure secret comparisons detected.
Container-Privileges	✅ Passed	PR only updates commit hashes in shell script version files; contains no container manifests, K8s configs, or privilege-escalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	PR only updates a commit hash in version config files; no sensitive data (passwords, tokens, keys, PII) is logged.
Title check	✅ Passed	The title accurately summarizes the main change: updating the openshift-test-private commit to a recent version across two configuration files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci-robot]

@kasturinarra: This pull request references USHIFT-7113 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

• Chores
• Updated test infrastructure configuration versions.

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.

[kasturinarra]

/test e2e-aws-tests-bootc-release-arm-el10

[kasturinarra]

@agullon could you please help review ?

pass log here for gingko tests: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_microshift/6790/pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm-el10/2061825680387084288

cc: @pmtk

[agullon]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, kasturinarra

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 [agullon,kasturinarra]

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

[kasturinarra]

/verified by CI

[openshift-ci-robot]

@kasturinarra: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

[kasturinarra]

/override ci/prow/e2e-aws-tests-bootc-release-arm-el10

[openshift-ci]

@kasturinarra: Overrode contexts on behalf of kasturinarra: ci/prow/e2e-aws-tests-bootc-release-arm-el10

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release-arm-el10

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.

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 9fbe865 and 2 for PR HEAD 0e8ba31 in total

[openshift-ci]

@kasturinarra: all tests passed!

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.