Need manually set boot from pxe when reinstall system

[xinzhongyoumeng]

What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.]

When I begin reinstall system, I need manually set boot from pxe, so that can reinstall system. Otherwise，the server only reboot. After reinstall system complete，reboot，it also boot from original system. What did you expect to happen:

When reinstall system complete, reboot ,it can boot from new system.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api version:
• Cluster-api-provider-metal3 version:
• Environment (metal3-dev-env or other):
• Kubernetes version: (use kubectl version):

/kind bug

[metal3-io-bot]

This issue is currently awaiting triage. If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance. The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[Rozzii]

At minimum we would need:

• The environment section to be populated with the relevant environment info in the issue
• We would need to know what BMC protocol were you using Redfish/IPMI etc
• We would need to know what is the content of the ironic config file in the ironic container /etc/ironic/ironic.conf
• Ironic logs would be also useful from the time period when the Ironic was unable to set the boot method correctly

[xinzhongyoumeng]

I see the log in ironic

install_bootloader: result "None", error "{'type': 'DeviceNotFound', 'code': 404, 'message': 'Error finding the disk or partition device to deploy the image onto', 'details': 'No partition with UUID 0xc65626fc found on device /dev/sda'}" get_commands_status /usr/lib/python3.9/site-packages/ironic/drivers/modules/agent_client.py:346

As a solution, I see the root device UUID by ironic cli can set

 baremetal node set $NODE_UUID --instance-info image_rootfs_uuid=<uuid>

but I can not find how to set this in metal3 bmh CR

[metal3-io-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Rozzii]

Do you still need help @xinzhongyoumeng /remove-lifecycle stale

[metal3-io-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[metal3-io-bot]

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

[metal3-io-bot]

@metal3-io-bot: Closing this issue.

In response to [this](https://github.com/metal3-io/cluster-api-provider-metal3/issues/1368#issuecomment-2276246755): >Stale issues close after 30d of inactivity. Reopen the issue with `/reopen`. Mark the issue as fresh with `/remove-lifecycle stale`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.