Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2025-12-24-095138_amd64-2025-12-24_arm64-2025-12-24#5982

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2025-12-24-095138_amd64-2025-12-24_arm64-2025-12-24
Dec 25, 2025
Merged

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2025-12-24-095138_amd64-2025-12-24_arm64-2025-12-24#5982
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2025-12-24-095138_amd64-2025-12-24_arm64-2025-12-24

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.17.0-0.nightly-2025-12-24-095138
arm64: 4.17.0-0.nightly-arm64-2025-12-24-095138
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2004039728101330944

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.17.0-0.nightly-2025-12-24-095138
arm64: 4.17.0-0.nightly-arm64-2025-12-24-095138
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2004039728101330944

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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.

@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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 Dec 25, 2025
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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 requested review from copejon and jogeo December 25, 2025 04:11
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 25, 2025

@microshift-rebase-script[bot]: 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.

@ggiguash
Copy link
Contributor

/lgtm
/verified by ci

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

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/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.

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

openshift-ci bot commented Dec 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, microshift-rebase-script[bot]

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 25, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit a11ef29 into release-4.17 Dec 25, 2025
20 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.17-4.17.0-0.nightly-2025-12-24-095138_amd64-2025-12-24_arm64-2025-12-24 branch December 25, 2025 07:16
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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants