-
Notifications
You must be signed in to change notification settings - Fork 87
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
Comments
This issue is currently awaiting triage. 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. |
At minimum we would need:
|
I see the log in ironic
As a solution, I see the root device UUID by ironic cli can set
but I can not find how to set this in metal3 bmh CR |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Do you still need help @xinzhongyoumeng |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues close after 30d of inactivity. Reopen the issue with /close |
@metal3-io-bot: Closing this issue. In response to this:
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. |
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:
kubectl version
):/kind bug
The text was updated successfully, but these errors were encountered: