NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2026-06-07-104958_amd64-2026-06-07_arm64-2026-06-08

[microshift-rebase-script]

amd64: 4.17.0-0.nightly-2026-06-07-104958
arm64: 4.17.0-0.nightly-arm64-2026-06-08-031617
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2063833553174532096

• router image-amd64 97662a3ac26c88d51b4e81bd794c33671868480d to cbd6d0481c2ddb72901fdbfb3c3d87a2867b1e2b

  • b4fc1a0 2026-05-26T17:17:15+00:00 Replace google.golang.org/grpc with github.com/openshift-sustaining/grpc-go v1.71.3-sec.1 to address CVE-2026-33186
  • 51f9f63 2026-05-26T17:17:14+00:00 UPSTREAM: : Vendor changes to address CVE-2026-33186

• router image-arm64 97662a3ac26c88d51b4e81bd794c33671868480d to cbd6d0481c2ddb72901fdbfb3c3d87a2867b1e2b

  • b4fc1a0 2026-05-26T17:17:15+00:00 Replace google.golang.org/grpc with github.com/openshift-sustaining/grpc-go v1.71.3-sec.1 to address CVE-2026-33186
  • 51f9f63 2026-05-26T17:17:14+00:00 UPSTREAM: : Vendor changes to address CVE-2026-33186

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

[microshift-rebase-script]

/verified by automatic-rebase

[openshift-ci-robot]

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

Details

In response to this:

amd64: 4.17.0-0.nightly-2026-06-07-104958
arm64: 4.17.0-0.nightly-arm64-2026-06-08-031617
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2063833553174532096

• router image-amd64 97662a3ac26c88d51b4e81bd794c33671868480d to cbd6d0481c2ddb72901fdbfb3c3d87a2867b1e2b

• b4fc1a0 2026-05-26T17:17:15+00:00 Replace google.golang.org/grpc with github.com/openshift-sustaining/grpc-go v1.71.3-sec.1 to address CVE-2026-33186

• 51f9f63 2026-05-26T17:17:14+00:00 UPSTREAM: : Vendor changes to address CVE-2026-33186

• router image-arm64 97662a3ac26c88d51b4e81bd794c33671868480d to cbd6d0481c2ddb72901fdbfb3c3d87a2867b1e2b

• b4fc1a0 2026-05-26T17:17:15+00:00 Replace google.golang.org/grpc with github.com/openshift-sustaining/grpc-go v1.71.3-sec.1 to address CVE-2026-33186

• 51f9f63 2026-05-26T17:17:14+00:00 UPSTREAM: : Vendor changes to address CVE-2026-33186

/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-robot]

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

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign eslutsky for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 01122db and 2 for PR HEAD 514f023 in total

[openshift-ci]

@microshift-rebase-script[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/metal-periodic-test-arm	514f023	link	true	/test metal-periodic-test-arm

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.