-
Notifications
You must be signed in to change notification settings - Fork 19
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
redfishpower: add extra timeout debug information #154
Conversation
Problem: in powerman.dev(5) the ranged scripts are typoed as "range". Correct the typoes.
Problem: Some text describing the selection of the status_all vs status scripts is invalid. Simply remove the offending text.
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.
LGTM - how do these changes interact with powerman? I.e. how does the user get the use ful information?
src/redfishpower/redfishpower.c
Outdated
/* strp - on, off, unknown | ||
* realstrp - on, off, poweringon, poweringoff, unknown | ||
*/ |
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.
Update comment for changed variable names?
Problem: There are times it would be convenient to know the actual redfish power status returned, rather than the internally mapped "on", "off", or "unknown" power status. Update parse_onoff() to optionally return additional redfish power status. The additional redfish power status returns are "paused", "powering off", and "powering on". Update variable names that call this function to be consistent.
Problem: When powering on a target, it will sometimes enter the "PoweringOn" state but regress back to the "off" state. This is likely due to a hardware problem. It can be hard to diagnose when the only clue is a power on has "timed out". Add some additional output to help diagnose this situation.
f4c4fd6
to
fe49841
Compare
At the moment they get it just via telemetry output. Not great, but it's something ... vs the nothing before this (I had to run redfishpower by hand in verbose mode and see what was going on). Once we work on #79 / #85, perhaps some of it can migrate to the user. |
thanks, setting MWP |
Problem: When powering on a target, it will sometimes enter the "PoweringOn" state but regress back to the "off" state. This is likely due to a hardware problem. It can be hard to diagnose when the only clue is a power on has "timed out".
Add some additional output to help diagnose this situation.
some cleanups added on top