NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2025-01-11-001833_amd64-2025-01-11_arm64-2025-01-11

[microshift-rebase-script]

amd64: 4.15.0-0.nightly-2025-01-11-001833
arm64: 4.15.0-0.nightly-arm64-2025-01-11-001836
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1878653460899958784

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

[openshift-ci-robot]

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

In response to this:

amd64: 4.15.0-0.nightly-2025-01-11-001833
arm64: 4.15.0-0.nightly-arm64-2025-01-11-001836
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1878653460899958784

/label tide/merge-method-squash
/label cherry-pick-approved
/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]

[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.

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

[pmtk]

All of the failed scenarios had trouble downloading topolvm images in similar way. Init container finished, then it tried to pull one of the images, but the pull never finished...
/retest

[pmtk]

Again... CRIO having trouble to pull topolvm images? Maybe registry.redhat.io is misbehaving...
/retest

[pacevedom]

/test metal-tests-arm

[openshift-ci]

@pacevedom: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test images

/test metal-periodic-test

/test metal-periodic-test-arm

/test microshift-metal-tests

/test microshift-metal-tests-arm

/test ocp-conformance-rhel-eus

/test ocp-conformance-rhel-eus-arm

/test test-rpm

/test test-unit

/test verify

The following commands are available to trigger optional jobs:

/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-release-4.15-images

pull-ci-openshift-microshift-release-4.15-microshift-metal-tests

pull-ci-openshift-microshift-release-4.15-microshift-metal-tests-arm

pull-ci-openshift-microshift-release-4.15-ocp-conformance-rhel-eus

pull-ci-openshift-microshift-release-4.15-ocp-conformance-rhel-eus-arm

pull-ci-openshift-microshift-release-4.15-test-rebase

pull-ci-openshift-microshift-release-4.15-test-unit

pull-ci-openshift-microshift-release-4.15-verify

In response to this:

/test metal-tests-arm

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.

[pacevedom]

/test microshift-metal-tests-arm

[pacevedom]

/test microshift-metal-tests-arm

[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/microshift-metal-tests-arm	48f8d2c	link	true	/test microshift-metal-tests-arm

Full PR test history. Your PR dashboard.

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.