Skip to content

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.22.0-0.nightly-2026-01-06-164201
arm64: 4.22.0-0.nightly-arm64-2026-01-14-031646
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2011287299525971968

  • coredns image-arm64 7486e9e4330c1e41d9a91e4673b7f2782efc112c to 45cf8aec34b207657d88a54f785cf09ae569d4fe

    • f523fe5 2026-01-05T18:23:09+00:00 Add team members to the OWNERS file
  • ovn-kubernetes image-arm64 904d66a2d4c674e35868a5c047a97c8a77f4a3fa to 1938041fd8f8c1fb5d376fa59faec1fef7614a92

  • service-ca-operator image-arm64 f5fde683e742dd5ddebcbfaf2d1a07fa96131a73 to 7c43fea353e9d13663e51e44788bf3c2ec737c1a

    • f750e73 2026-01-12T19:37:30+08:00 test/e2e: migrate serving-cert-secret-delete-data test for OTE compatibility
    • 685de04 2026-01-12T13:37:39+08:00 test/e2e: migrate serving-cert-secret-add-data test for OTE compatibility
    • f0218f8 2026-01-09T21:27:32+08:00 test/e2e: migrate serving-cert-secret-modify-bad-tlsCert test for OTE compatibility

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

@microshift-rebase-script
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-release-4.20-4.20.0-0.nightly-2026-01-08-043322_amd64-2026-01-08_arm64-2026-01-11

@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 14, 2026
@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jan 14, 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-06-164201
arm64: 4.22.0-0.nightly-arm64-2026-01-14-031646
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2011287299525971968

  • coredns image-arm64 7486e9e4330c1e41d9a91e4673b7f2782efc112c to 45cf8aec34b207657d88a54f785cf09ae569d4fe

  • f523fe5 2026-01-05T18:23:09+00:00 Add team members to the OWNERS file

  • ovn-kubernetes image-arm64 904d66a2d4c674e35868a5c047a97c8a77f4a3fa to 1938041fd8f8c1fb5d376fa59faec1fef7614a92

  • 58296b6d 2025-12-20T11:48:57+00:00 Updating ovn-kubernetes-microshift-container image to be consistent with ART for 4.22 Reconciling with https://github.com/openshift/ocp-build-data/tree/087d1930e36b609f77d73bd8a313d85c940cff4d/images/ovn-kubernetes-microshift.yml

  • service-ca-operator image-arm64 f5fde683e742dd5ddebcbfaf2d1a07fa96131a73 to 7c43fea353e9d13663e51e44788bf3c2ec737c1a

  • f750e73 2026-01-12T19:37:30+08:00 test/e2e: migrate serving-cert-secret-delete-data test for OTE compatibility

  • 685de04 2026-01-12T13:37:39+08:00 test/e2e: migrate serving-cert-secret-add-data test for OTE compatibility

  • f0218f8 2026-01-09T21:27:32+08:00 test/e2e: migrate serving-cert-secret-modify-bad-tlsCert 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 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 14, 2026
@openshift-ci openshift-ci bot requested review from copejon and vanhalenar January 14, 2026 04:15
@pacevedom
Copy link
Contributor

/retest

2 similar comments
@pacevedom
Copy link
Contributor

/retest

@pacevedom
Copy link
Contributor

/retest

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
/verified by CI

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

openshift-ci bot commented Jan 14, 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 14, 2026
@ggiguash
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 14, 2026
@openshift-ci-robot
Copy link

@ggiguash: 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
Copy link
Contributor

openshift-ci bot commented Jan 14, 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 0179241 into main Jan 14, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.22-4.22.0-0.nightly-2026-01-06-164201_amd64-2026-01-06_arm64-2026-01-14 branch January 14, 2026 18:10
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.

3 participants