Skip to content

[release-4.20] NO-ISSUE: Update openshift-test-private commit#5604

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
agullon:update_openshift-test-private_commit
Oct 15, 2025
Merged

[release-4.20] NO-ISSUE: Update openshift-test-private commit#5604
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
agullon:update_openshift-test-private_commit

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Oct 13, 2025

Update openshift-test-private commit to the latest one at this moment

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 13, 2025
@openshift-ci-robot
Copy link

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

Update openshift-test-private commit to the latest one at this moment

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@agullon agullon force-pushed the update_openshift-test-private_commit branch from 70a9299 to 89d856d Compare October 13, 2025 12:11
@agullon
Copy link
Contributor Author

agullon commented Oct 13, 2025

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

@agullon
Copy link
Contributor Author

agullon commented Oct 13, 2025

/retest

@kasturinarra
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

[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:

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

@agullon
Copy link
Contributor Author

agullon commented Oct 14, 2025

/verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025
@openshift-ci-robot
Copy link

@agullon: This PR has been marked as verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test.

Details

In response to this:

/verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test

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.

@pacevedom
Copy link
Contributor

/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 14, 2025
@ggiguash
Copy link
Contributor

/retitle [release-4.20] NO-ISSUE: Update openshift-test-private commit

@openshift-ci openshift-ci bot changed the title NO-ISSUE: Update openshift-test-private commit [release-4.20] NO-ISSUE: Update openshift-test-private commit Oct 15, 2025
@agullon
Copy link
Contributor Author

agullon commented Oct 15, 2025

@jerpeter1 can you please review this PR? thanks

@sdodson
Copy link
Member

sdodson commented Oct 15, 2025

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 15, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 13478af and 2 for PR HEAD 89d856d in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 15, 2025

@agullon: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 17d1d9a into openshift:release-4.20 Oct 15, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants