Skip to content

NO-ISSUE: rebase-release-4.21-4.21.0-0.nightly-2026-01-22-192129_amd64-2026-01-22_arm64-2026-01-26#6152

Merged
openshift-merge-bot[bot] merged 3 commits intorelease-4.21from
rebase-release-4.21-4.21.0-0.nightly-2026-01-22-192129_amd64-2026-01-22_arm64-2026-01-26
Jan 27, 2026
Merged

NO-ISSUE: rebase-release-4.21-4.21.0-0.nightly-2026-01-22-192129_amd64-2026-01-22_arm64-2026-01-26#6152
openshift-merge-bot[bot] merged 3 commits intorelease-4.21from
rebase-release-4.21-4.21.0-0.nightly-2026-01-22-192129_amd64-2026-01-22_arm64-2026-01-26

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.21.0-0.nightly-2026-01-22-192129
arm64: 4.21.0-0.nightly-arm64-2026-01-26-231543
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/2015998603754999808

/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 Jan 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

amd64: 4.21.0-0.nightly-2026-01-22-192129
arm64: 4.21.0-0.nightly-arm64-2026-01-26-231543
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/2015998603754999808

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

@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 Jan 27, 2026
Copy link
Copy Markdown
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jan 27, 2026
@pacevedom
Copy link
Copy Markdown
Contributor

/verified by CI

@openshift-ci-robot
Copy link
Copy Markdown

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

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jan 27, 2026

@microshift-rebase-script: 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 e627284 into release-4.21 Jan 27, 2026
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.21-4.21.0-0.nightly-2026-01-22-192129_amd64-2026-01-22_arm64-2026-01-26 branch January 27, 2026 08:25
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