use Orion latest tag for olm

[jianzhangbjz]

Use the latest tag to avoid the scenario below from happening https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test/1960870117323575296. And, https://redhat-internal.slack.com/archives/CNKHL6076/p1756370914827749?thread_ts=1755484862.890019&cid=CNKHL6076

+ git clone --branch v0.0.23 https://github.com/cloud-bulldozer/orion.git --depth 1
Cloning into 'orion'...
warning: Could not find remote branch v0.0.23 to clone.
fatal: Remote branch v0.0.23 not found in upstream origin

[jianzhangbjz]

/pj-rehearse periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test

[openshift-ci-robot]

@jianzhangbjz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[chentex]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chentex, jianzhangbjz

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

The pull request process is described here

Needs approval from an approver in each of these files:

• ci-operator/step-registry/openshift-qe/orion/olmv1/OWNERS [jianzhangbjz]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[jianzhangbjz]

/pj-rehearse periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test

[openshift-ci-robot]

@jianzhangbjz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@jianzhangbjz: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-olmv1-benchmark-test	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-olmv1-benchmark-test	N/A	periodic	Registry content changed
periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test	N/A	periodic	Registry content changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@jianzhangbjz: The following test 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/rehearse/periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test	6b8974f	link	unknown	/pj-rehearse periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-gcp-4.19-nightly-x86-olmv1-benchmark-test

Full PR test history. Your PR dashboard.

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.