-
Notifications
You must be signed in to change notification settings - Fork 171
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
[OpenBMC] Support bootmode generically #4727
Conversation
- isn't numeric in numeric ne (!=) - Scalar value @attr_value[-1] better written as $attr_value[-1]
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me
hi, @whowutwut , why not implement the boot mode interface to rsetboot as I suggest in https://ibm-systems-storage.slack.com/archives/C68N2UK0X/p1516868331000070?thread_ts=1516820529.000339&cid=C68N2UK0X? |
@zet809 What would be the suggested interface here if we tagged to The rsetboot is temporarily setting the next boot of the server, where this bootmode in my opinion is really a debug attribute. The use case here is to run across a large number of systems and make sure that the value is "Regular" I don't think customer should be modifying the value, but we allow a get/set based on our generic code support. MFG uses it when pre-loading the server, but should return the value to Regular when it ships. So really, adding this attribute is really to help us use xCAT to debug systems in the field. |
Hi, @whowutwut , I think you are right that bootmode mainly useful for debugging. |
Resolves #4718 |
@zet809 Yes, bootmode controls the behavior I believe up to Petitboot... when the host IPLs.. |
This function is used to view/set the host bootmode. This is really added to help debug some strange issues that we are seeing where certain machines are stopping at Petitboot and not booting off the network on first discovery.
The 4th commit is related to PowerSupplyRedundancy (tag #4715) in that the value takes effect on a IPL, not a bmc reboot. A bmcreboot actually removes the setting.
I'd like to get this into the 2.13.10 release tomorrow.
UT:
On errror, we would see the following msg: