-
Notifications
You must be signed in to change notification settings - Fork 64
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
[sidero] encountered error discovering BMC IP. skipping setup: "..." rebooting in 10 seconds #988
Comments
But perhaps I misunderstandood how Sidero work, as that reboot still happens, after getting rid of that error. So the reboots are not because of the "error discovering BMC IP", but because... the server isn't allocated, yet? So... onwards to https://www.sidero.dev/v0.5/getting-started/create-workload, to stop it from constantly rebooting, I guess that's the idea here; will try ASAP. |
Explain how to set --auto-bmc-setup=false using SIDERO_CONTROLLER_MANAGER_AUTO_BMC_SETUP. Signed-off-by: Michael Vorburger <[email protected]>
Let me close this issue, as I think it was a misunderstanding on my part. (#989 would still be useful to clarify that, IMHO.) |
Explain how to set --auto-bmc-setup=false using SIDERO_CONTROLLER_MANAGER_AUTO_BMC_SETUP. Signed-off-by: Michael Vorburger <[email protected]> Signed-off-by: Andrey Smirnov <[email protected]>
Explain how to set --auto-bmc-setup=false using SIDERO_CONTROLLER_MANAGER_AUTO_BMC_SETUP. Signed-off-by: Michael Vorburger <[email protected]> Signed-off-by: Andrey Smirnov <[email protected]>
I'm a first time user attempting to set up Sidero at home, and after much fun with PXE etc. got blocked here, it "loops" with this on the console:
I gather that perhaps I need to somehow tell it that this (nor any of my) machine doesn't have that?
I couldn't quite figure out yet how to tell it not do that from the doc, but I'll keep looking.
In the mean time, perhaps you would like to consider handling this more gracefully, and not bail like this on machines without IPMI?
The text was updated successfully, but these errors were encountered: