Skip to content

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-01-14-031657_amd64-2026-01-14_arm64-2026-01-19#6103

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

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-01-14-031657_amd64-2026-01-14_arm64-2026-01-19#6103
openshift-merge-bot[bot] merged 5 commits intomainfrom
rebase-release-4.22-4.22.0-0.nightly-2026-01-14-031657_amd64-2026-01-14_arm64-2026-01-19

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.22.0-0.nightly-2026-01-14-031657
arm64: 4.22.0-0.nightly-arm64-2026-01-19-012506
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2013099495289524224

  • oc image-arm64 4df0e94abe472105343c5c132396fbfafa47c569 to 430c82293109e23f3caaf9ba60e5affd2d5356f5

    • 4f7cc648 2026-01-16T09:12:56+03:00 Fix unit test failure by updating ruby version to 3.3
  • kubernetes image-arm64 581cfc7ee3313c212378878350aec16236e3f155 to e4a4167c40c9ed543c5a80f2e08cc73696f7a4f6

    • 11bb75887 2026-01-16T10:25:44-05:00 UPSTREAM: 135340: cbor: bump limits
    • a0f87aee4 2026-01-15T21:44:31+08:00 UPSTREAM: : change iperf2 test case from parallel into serial
  • service-ca-operator image-arm64 bb522851659b55683ff29410ee1a300af1506926 to 503e4f5f4c74fd095a8dca385541125f3c9ee28b

    • aaba756 2026-01-16T15:51:27+08:00 test/e2e: migrate metrics tests for OTE compatibility
    • c9f6639 2026-01-15T20:26:00+08:00 test/e2e: migrate headless-stateful-serving-cert-secret-delete-data test for OTE compatibility

/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 19, 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-14-031657
arm64: 4.22.0-0.nightly-arm64-2026-01-19-012506
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2013099495289524224

  • oc image-arm64 4df0e94abe472105343c5c132396fbfafa47c569 to 430c82293109e23f3caaf9ba60e5affd2d5356f5

  • 4f7cc648 2026-01-16T09:12:56+03:00 Fix unit test failure by updating ruby version to 3.3

  • kubernetes image-arm64 581cfc7ee3313c212378878350aec16236e3f155 to e4a4167c40c9ed543c5a80f2e08cc73696f7a4f6

  • 11bb75887 2026-01-16T10:25:44-05:00 UPSTREAM: 135340: cbor: bump limits

  • a0f87aee4 2026-01-15T21:44:31+08:00 UPSTREAM: : change iperf2 test case from parallel into serial

  • service-ca-operator image-arm64 bb522851659b55683ff29410ee1a300af1506926 to 503e4f5f4c74fd095a8dca385541125f3c9ee28b

  • aaba756 2026-01-16T15:51:27+08:00 test/e2e: migrate metrics tests for OTE compatibility

  • c9f6639 2026-01-15T20:26:00+08:00 test/e2e: migrate headless-stateful-serving-cert-secret-delete-data test for OTE compatibility

/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 19, 2026
@pacevedom
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 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-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 19, 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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 19, 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 19, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit e0a7620 into main Jan 19, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.22-4.22.0-0.nightly-2026-01-14-031657_amd64-2026-01-14_arm64-2026-01-19 branch January 19, 2026 09:24
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