**FAILURE** rebase-release-4.17-4.17.0-0.nightly-2026-02-22-233331_amd64-2026-02-22_arm64-2026-02-23

[microshift-rebase-script]

rebase.sh failed - check committed rebase_sh.log

amd64: 4.17.0-0.nightly-2026-02-22-233331
arm64: 4.17.0-0.nightly-arm64-2026-02-23-001612
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2025783039828692992

• machine-config-operator embedded-component 247c2c7ff38913836a0ff6c469e80b82df8cb5a5 to 1b370d9158cc914760dfc4ef5508d8634ede0f2e

  • 6f0b00b4 2026-02-05T11:35:21-06:00 PIS
  • 1dedbe7a 2026-02-05T11:27:40-06:00 check if the MachineOSConfig CRD exists before starting the informer
  • 868a609f 2026-01-20T11:27:09-06:00 WaitForCacheSync blocks forever

• operator-framework-olm embedded-component 52652d0744d7cf955defb84d38f45bfe640d7850 to e92a5cf8d93f756e47646aaf8f064f656a5f27dd

  • aa2ff0b4 2026-02-16T15:40:24+00:00 fixup! Remove the collect-profiles job
  • e293a216 2026-02-16T15:40:24+00:00 fixup! Remove the collect-profiles job
  • 21d30d28 2026-02-16T15:40:24+00:00 Remove the collect-profiles job

/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]: 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 pliurh 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-ci]

@microshift-rebase-script[bot]: The following tests 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/test-unit	46efeff	link	true	/test test-unit
ci/prow/microshift-metal-cache	46efeff	link	true	/test microshift-metal-cache
ci/prow/test-rebase	46efeff	link	false	/test test-rebase
ci/prow/ocp-full-conformance-rhel-eus	46efeff	link	true	/test ocp-full-conformance-rhel-eus
ci/prow/metal-bootc-periodic-test-arm	46efeff	link	true	/test metal-bootc-periodic-test-arm
ci/prow/microshift-metal-cache-arm	46efeff	link	true	/test microshift-metal-cache-arm
ci/prow/metal-bootc-test-arm	46efeff	link	true	/test metal-bootc-test-arm
ci/prow/microshift-metal-tests	46efeff	link	true	/test microshift-metal-tests
ci/prow/verify	46efeff	link	true	/test verify
ci/prow/microshift-metal-tests-arm	46efeff	link	true	/test microshift-metal-tests-arm
ci/prow/metal-periodic-test	46efeff	link	true	/test metal-periodic-test
ci/prow/footprint-and-performance	46efeff	link	true	/test footprint-and-performance
ci/prow/metal-periodic-test-arm	46efeff	link	true	/test metal-periodic-test-arm
ci/prow/metal-bootc-periodic-test	46efeff	link	true	/test metal-bootc-periodic-test
ci/prow/e2e-aws-nvidia-device-plugin	46efeff	link	true	/test e2e-aws-nvidia-device-plugin
ci/prow/ocp-conformance-with-optional-rpms-rhel-eus-nightly-arm	46efeff	link	true	/test ocp-conformance-with-optional-rpms-rhel-eus-nightly-arm
ci/prow/metal-bootc-test	46efeff	link	true	/test metal-bootc-test
ci/prow/ocp-conformance-with-optional-rpms-rhel-eus-nightly	46efeff	link	true	/test ocp-conformance-with-optional-rpms-rhel-eus-nightly

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.