Skip to content

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2026-02-05-031206_amd64-2026-02-05_arm64-2026-02-05#6199

Merged
openshift-merge-bot[bot] merged 9 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2026-02-05-031206_amd64-2026-02-05_arm64-2026-02-05
Feb 10, 2026
Merged

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2026-02-05-031206_amd64-2026-02-05_arm64-2026-02-05#6199
openshift-merge-bot[bot] merged 9 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2026-02-05-031206_amd64-2026-02-05_arm64-2026-02-05

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.16.0-0.nightly-2026-02-05-031206
arm64: 4.16.0-0.nightly-arm64-2026-02-05-153004
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/2019436755660312576

  • cluster-network-operator embedded-component e83d7d8449cff5fe79978f2e19971aad5aff5edc to e0302b4751a6fb567a2635e537df8e78ee8ee9ee

    • f3d55af 2025-08-11T15:22:46+00:00 Update CNO reviwers/approvers
  • kubernetes embedded-component 7b5d27f7df0938daa221007d80cf397885480af2 to c80debdd0580ea09f2359ac9c3297a2afd24bdc6

    • b08b88ed7 2026-01-22T16:34:57+01:00 UPSTREAM: : Skip e2e test: attach on previously attached volumes should work
  • kubernetes image-amd64 7b5d27f7df0938daa221007d80cf397885480af2 to c80debdd0580ea09f2359ac9c3297a2afd24bdc6

    • b08b88ed7 2026-01-22T16:34:57+01:00 UPSTREAM: : Skip e2e test: attach on previously attached volumes should work
  • kubernetes image-arm64 7b5d27f7df0938daa221007d80cf397885480af2 to c80debdd0580ea09f2359ac9c3297a2afd24bdc6

    • b08b88ed7 2026-01-22T16:34:57+01:00 UPSTREAM: : Skip e2e test: attach on previously attached volumes should work

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

@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@ggiguash
Copy link
Contributor

ggiguash commented Feb 7, 2026

/approved
/test all

@openshift-ci
Copy link
Contributor

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

@pacevedom
Copy link
Contributor

/label jira/valid-bug
/label backport-risk-assessed
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 10, 2026
@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 10, 2026
@openshift-ci-robot
Copy link

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/label jira/valid-bug
/label backport-risk-assessed
/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 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 10, 2026
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

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

openshift-ci bot commented Feb 10, 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 Feb 10, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit e26a8ee into release-4.16 Feb 10, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.16-4.16.0-0.nightly-2026-02-05-031206_amd64-2026-02-05_arm64-2026-02-05 branch February 10, 2026 08:27
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. lgtm Indicates that a PR is ready to be merged. 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