We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
As Redfish Schema Supplement document, the PowerRestorePolicy defined: AlwaysOff, AlwaysOn, LastState
The bmcweb is handle this already
But, dbus-interfaces does not handle the "LastState" enumerations. It just defines AlwaysOff, AlwaysOn, Restore. https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Control/Power/RestorePolicy.interface.yaml
Why is a mismatch between Redfish specification and phosphor-dbus-interface? Should it be changed to "LastState" instead of "Restore"?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
As Redfish Schema Supplement document, the PowerRestorePolicy defined: AlwaysOff, AlwaysOn, LastState

The bmcweb is handle this already

But, dbus-interfaces does not handle the "LastState" enumerations. It just defines AlwaysOff, AlwaysOn, Restore.
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Control/Power/RestorePolicy.interface.yaml
Why is a mismatch between Redfish specification and phosphor-dbus-interface? Should it be changed to "LastState" instead of "Restore"?
The text was updated successfully, but these errors were encountered: