Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need manually set boot from pxe when reinstall system #1368

Open
xinzhongyoumeng opened this issue Dec 19, 2023 · 5 comments
Open

Need manually set boot from pxe when reinstall system #1368

xinzhongyoumeng opened this issue Dec 19, 2023 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@xinzhongyoumeng
Copy link

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 metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Dec 19, 2023
@metal3-io-bot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Rozzii
Copy link
Member

Rozzii commented Dec 20, 2023

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

@Rozzii Rozzii added the triage/needs-information Indicates an issue needs more information in order to work on it. label Dec 20, 2023
@xinzhongyoumeng
Copy link
Author

xinzhongyoumeng commented Dec 21, 2023

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
Copy link
Contributor

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 metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 20, 2024
@Rozzii
Copy link
Member

Rozzii commented Apr 10, 2024

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

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants