2b51921cc7
Add expected_power_state parameter to _wait_for_power_state_stable() to ensure rescue operations actually power on instances. Previously, the method only checked if power state was stable, not if it matched the expected state. This caused false success reports when rescue failed to power on instances, leading to 120s timeouts in Ironic. Now logs detailed diagnostics including fault info and full instance data when power state verification fails, enabling faster debugging. Assisted-By: Claude (claude-4.5-sonnet) Change-Id: Ibf6934943af96c9a2594621f23f570a5e2e03f7d Signed-off-by: Harald Jensås <[email protected]>
Redfish development tools
This is a set of simple simulation tools aimed at supporting the development and testing of the Redfish protocol implementations and, in particular, the Sushy library (https://docs.openstack.org/sushy/). It is not designed for use outside of development and testing environments. Please do not run sushy-tools in a production environment of any kind.
The package ships two simulators - the static Redfish responder and the virtual Redfish BMC (which is backed by libvirt or OpenStack cloud).
The static Redfish responder is a simple REST API server which responds with the same things to client queries. It is effectively read-only.
The virtual Redfish BMC resembles the real Redfish-controlled bare metal machine to some extent. Some client queries are translated to commands that actually control VM instances simulating bare metal hardware. However, some of the Redfish commands just return static content, never touching the virtualization backend and in this regard, the virtual Redfish BMC is similar to the static Redfish responder.
- Free software: Apache license
- Documentation: https://docs.openstack.org/sushy-tools
- Source: http://opendev.org/openstack/sushy-tools
- Bugs: https://storyboard.openstack.org/#!/project/openstack/sushy-tools