NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2025-01-08-181146_amd64-2025-01-08_arm64-2025-01-08

[microshift-rebase-script]

amd64: 4.15.0-0.nightly-2025-01-08-181146
arm64: 4.15.0-0.nightly-arm64-2025-01-08-233730
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1877203878278074368

/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-08-181146
arm64: 4.15.0-0.nightly-arm64-2025-01-08-233730
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1877203878278074368

/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 pmtk 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

[ggiguash]

/test microshift-metal-tests-arm

[pmtk]

/retest microshift-metal-tests-arm

In both failed scenarios, the dns-resolver's image was stuck downloading (cli image which was updated in this PR btw). I don't know why only two scenarios failed in each job. It reminds me of a problem we had very long time ago where images would be stuck downloading on crio level, but I don't recall the details.
If this retest doesn't clear the error, I'd drop the PR and wait for the next one.

[openshift-ci]

@pmtk: The /retest command does not accept any targets.
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:

/retest microshift-metal-tests-arm

In both failed scenarios, the dns-resolver's image was stuck downloading (cli image which was updated in this PR btw). I don't know why only two scenarios failed in each job. It reminds me of a problem we had very long time ago where images would be stuck downloading on crio level, but I don't recall the details.
If this retest doesn't clear the error, I'd drop the PR and wait for the next one.

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.

[pmtk]

/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	6c3a91b	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.

[pmtk]

In the most recent fail there are things I cannot explain.
In one job, only 3 images were downloaded and ovnkube-master didn't start (funny thing is that ovnk-master's image wasn't downloaded, ovnk-node's was but they're the same image...).
In other image for node-resolver wasn't even attempted to pull (and this is 4.14 because it's an upgrade test). Other time it cannot create pod for node-resolver because "name is already reserved".

I think it might be best to close the PR and see how next rebase works...