Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2026-04-01-100551_amd64-2026-04-01_arm64-2026-04-01#6452

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2026-04-01-100551_amd64-2026-04-01_arm64-2026-04-01
Apr 2, 2026
Merged

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2026-04-01-100551_amd64-2026-04-01_arm64-2026-04-01#6452
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2026-04-01-100551_amd64-2026-04-01_arm64-2026-04-01

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.17.0-0.nightly-2026-04-01-100551
arm64: 4.17.0-0.nightly-arm64-2026-04-01-222329
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2039553730327613440

  • ovn-kubernetes image-amd64 0fb1abde1454b64b596657600e18f4196229fa5a to af9d912e101fe65cc197e7d0b06182c82d7368f3

    • cab5ac8d 2026-03-09T15:26:51+01:00 Add pperiyasamy to OWNERS for release-4.17
  • ovn-kubernetes image-arm64 0fb1abde1454b64b596657600e18f4196229fa5a to af9d912e101fe65cc197e7d0b06182c82d7368f3

    • cab5ac8d 2026-03-09T15:26:51+01:00 Add pperiyasamy to OWNERS for release-4.17

/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 Apr 2, 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.17.0-0.nightly-2026-04-01-100551
arm64: 4.17.0-0.nightly-arm64-2026-04-01-222329
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2039553730327613440

  • ovn-kubernetes image-amd64 0fb1abde1454b64b596657600e18f4196229fa5a to af9d912e101fe65cc197e7d0b06182c82d7368f3

  • cab5ac8d 2026-03-09T15:26:51+01:00 Add pperiyasamy to OWNERS for release-4.17

  • ovn-kubernetes image-arm64 0fb1abde1454b64b596657600e18f4196229fa5a to af9d912e101fe65cc197e7d0b06182c82d7368f3

  • cab5ac8d 2026-03-09T15:26:51+01:00 Add pperiyasamy to OWNERS for release-4.17

/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
Copy Markdown
Contributor Author

/verified by automatic-rebase

@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 Apr 2, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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 requested review from copejon and jerpeter1 April 2, 2026 04:28
@eslutsky
Copy link
Copy Markdown
Contributor

eslutsky commented Apr 2, 2026

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 2, 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.

@eslutsky
Copy link
Copy Markdown
Contributor

eslutsky commented Apr 2, 2026

/lgtm
/verified by ci

Added by microshift-prow-jobs-for-pull-requests.sh 🤖

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 2, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@eslutsky: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/verified by ci

Added by microshift-prow-jobs-for-pull-requests.sh 🤖

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
Copy Markdown
Contributor

openshift-ci Bot commented Apr 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Apr 2, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit e361156 into release-4.17 Apr 2, 2026
20 checks passed
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.17-4.17.0-0.nightly-2026-04-01-100551_amd64-2026-04-01_arm64-2026-04-01 branch April 2, 2026 10:18
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