diff options
| author | Aija Jauntēva <aija.jaunteva@dell.com> | 2021-09-08 11:20:20 -0400 |
|---|---|---|
| committer | Aija Jauntēva <aija.jaunteva@dell.com> | 2021-09-14 16:02:54 +0000 |
| commit | 2a0fd1d13f178c9872330cf6498dc25572a721da (patch) | |
| tree | 2d93fd8a8c6025912cb6dbb41803cc141114a1af /releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml | |
| parent | 743f206d0765da1e7eb97da01117947f7a968710 (diff) | |
| download | ironic-2a0fd1d13f178c9872330cf6498dc25572a721da.tar.gz | |
Fix idrac-wsman set_power_state to wait on HW
set_power_state has returned to the caller immediately without
confirming the system has reached the requested state. This fixes that
by synchronously waiting until the target state has been read before
returning.
That bug can cause instance workload deployments to fail on Dell EMC
PowerEdge server models on which IPA ramdisk soft power off fails and
ironic employs its OOB fallback strategy. After an otherwise successful
deployment, the node is active, but is powered off. No error is reported
in last_error. If the subsequent instance workflow expects the system to
be powered on into the operating system, it fails.
Story: 2009204
Task: 43261
Change-Id: I3112a22149c07e5508f26c79f33d09aeb905c308
Diffstat (limited to 'releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml')
| -rw-r--r-- | releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml b/releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml new file mode 100644 index 000000000..4ac895625 --- /dev/null +++ b/releasenotes/notes/idrac-wsman-set-power-state-wait-cd8f9ff41b19c7a7.yaml @@ -0,0 +1,10 @@ +--- +fixes: + - | + Fixes ``idrac-wsman`` power interface to wait for the hardware to reach the + target state before returning. For systems where soft power off at the end + of deployment to boot to instance failed and forced hard power off was + used, this left node successfully deployed in off state without any errors. + This broke other workflows expecting node to be on booted into + OS at the end of deployment. Additional information can be found in + `story 2009204 <https://storyboard.openstack.org/#!/story/2009204>`_. |