Browse Source

Extend power sync timeout for Ericsson SDI

Ericsson SDI uses cached power state data in what is returned
to the API user, and typically this takes longer than 30 seconds
to provide an updated value to the API user.

As such, if we do not extend the timeout value, such users of
Ironic's Redfish API interface will have deployments fail as
the power state timeout will be encountered.

This change landed in ussuri, and is proposed to stable/train due to
TripleO CI failures.

Related-Bug: #1947403
Change-Id: I0aa5131504b60b13d43c73c9a3be1f50f7855cbc
(cherry picked from commit 4383303dfb)
changes/72/815572/1
Julia Kreger 2 years ago committed by Steve Baker
parent
commit
31c7469a91
  1. 2
      ironic/conf/conductor.py
  2. 9
      releasenotes/notes/conductor-power-sync-timeout-extension-fa5e7b5fdd679d84.yaml

2
ironic/conf/conductor.py

@ -209,7 +209,7 @@ opts = [
help=_('Timeout (in seconds) of soft reboot and soft power '
'off operation. This value always has to be positive.')),
cfg.IntOpt('power_state_change_timeout',
min=2, default=30,
min=2, default=60,
help=_('Number of seconds to wait for power operations to '
'complete, i.e., so that a baremetal node is in the '
'desired power state. If timed out, the power operation '

9
releasenotes/notes/conductor-power-sync-timeout-extension-fa5e7b5fdd679d84.yaml

@ -0,0 +1,9 @@
---
other:
- |
The ``[conductor]power_state_change_timeout`` default value has been
extended to ``60`` seconds from ``30`` seconds. This is due to some
API interfaces with Redfish, may cache the power state and thus may
take longer than thirty seconds to update after a change has been
requested. Please see `here <https://github.com/metal3-io/ironic-image/issues/143>`_
for more information.
Loading…
Cancel
Save