Skip to content

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-01-22-122134_amd64-2026-01-22_arm64-2026-01-23#6134

Merged
openshift-merge-bot[bot] merged 5 commits intomainfrom
rebase-release-4.22-4.22.0-0.nightly-2026-01-22-122134_amd64-2026-01-22_arm64-2026-01-23
Jan 23, 2026
Merged

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-01-22-122134_amd64-2026-01-22_arm64-2026-01-23#6134
openshift-merge-bot[bot] merged 5 commits intomainfrom
rebase-release-4.22-4.22.0-0.nightly-2026-01-22-122134_amd64-2026-01-22_arm64-2026-01-23

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.22.0-0.nightly-2026-01-22-122134
arm64: 4.22.0-0.nightly-arm64-2026-01-23-020204
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2014548855588130816

  • api embedded-component 4c643a652d54d4d2a06c1ebdb1350abcb568c07f to 59aa3e50a9fb94f93ab0f86649db2bab6ef61f01

    • 98cf8463 2026-01-20T10:50:03-05:00 chore(tools): bump controller-tools with stable slice sort fix
    • e87c917e 2026-01-20T09:30:17-06:00 NO-JIRA: Fix Infrastructure PlatformType comment
  • cluster-kube-apiserver-operator embedded-component 1aee49b41513b3d263bd9a1b7670286e5898565e to f4181f9afff1d9592ee98c9be7613b93554279d0

    • 850daef 2026-01-21T15:44:02+05:30 Migrating user_client_ca_test to ginkgo
  • cluster-kube-scheduler-operator embedded-component f56b603a018af8ec2ff6fcb3a72cb8dc3f28b3e5 to ed10ad69474b83c568452f59dbd3d943778799d7

    • aba7c9a 2026-01-16T10:33:45+01:00 Add OPERATOR_IMAGE_VERSION to recovery container

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

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

Details

In response to this:

amd64: 4.22.0-0.nightly-2026-01-22-122134
arm64: 4.22.0-0.nightly-arm64-2026-01-23-020204
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2014548855588130816

  • api embedded-component 4c643a652d54d4d2a06c1ebdb1350abcb568c07f to 59aa3e50a9fb94f93ab0f86649db2bab6ef61f01

  • 98cf8463 2026-01-20T10:50:03-05:00 chore(tools): bump controller-tools with stable slice sort fix

  • e87c917e 2026-01-20T09:30:17-06:00 NO-JIRA: Fix Infrastructure PlatformType comment

  • cluster-kube-apiserver-operator embedded-component 1aee49b41513b3d263bd9a1b7670286e5898565e to f4181f9afff1d9592ee98c9be7613b93554279d0

  • 850daef 2026-01-21T15:44:02+05:30 Migrating user_client_ca_test to ginkgo

  • cluster-kube-scheduler-operator embedded-component f56b603a018af8ec2ff6fcb3a72cb8dc3f28b3e5 to ed10ad69474b83c568452f59dbd3d943778799d7

  • aba7c9a 2026-01-16T10:33:45+01:00 Add OPERATOR_IMAGE_VERSION to recovery container

/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

Extra messages:

  • Deleted following branches: rebase-4.18.0-0.nightly_amd64-2026-01-21-231241_arm64-2026-01-22-025221

@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 23, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

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

Copy link
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

@pacevedom
Copy link
Contributor

/verified by CI

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

openshift-ci bot commented Jan 23, 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 23, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 23, 2026
@openshift-ci-robot
Copy link

@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-merge-bot openshift-merge-bot bot merged commit 388ac0c into main Jan 23, 2026
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.22-4.22.0-0.nightly-2026-01-22-122134_amd64-2026-01-22_arm64-2026-01-23 branch January 23, 2026 09:01
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