openstack/ironic
Code Issues Proposed changes

Merge "Release note updates for Victoria release"

Browse Source
This commit is contained in:
Zuul 2020-09-24 09:32:34 +00:00 committed by Gerrit Code Review
commit d2b5007c9e
4 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
releasenotes/notes/add-iso-suffix-557a4fc4382fd7f3.yaml
View File

@ -1,6 +1,7 @@
---
fixes:
- |
Add the suffix ".iso" for the ISO images generated by Ironic, as some
hardwares can not load the ISO images if they are not suffixed with
".iso". It is also recommended to name the files with proper extensions.
Fixes compatability with some hardware that requires the file name of
any virtual media to end with the suffix ".iso" when Ironic generates
a virtual media image. We recommend operators generating their own
virtual media files to name the files with proper extensions.

3
releasenotes/notes/fast-track-steps-81bd79a2a91e1b30.yaml
View File

@ -4,4 +4,5 @@ fixes:
Fixes an issue that caused in-band deploy steps inserted before
``write_image`` to be skipped when fast-track is used.
- |
Makes sure in-band deploy and clean steps are not cached across reboots.
Fixes an issue where in-band deploy and clean steps were being
cached across reboots of the agent.

7
releasenotes/notes/ilo5-oob-one-button-secure-erase-f55628f8aa767c20.yaml
View File

@ -4,7 +4,6 @@ features:
operation for iLO5 based HPE Proliant servers as a ``management``
clean step ``one_button_secure_erase`` for ``ilo5`` hardware type.
upgrade:
- The ``do_one_button_secure_erase`` interface of 'proliantutils' library has
been enhanced to support out-of-band one button secure erase operation for
``ilo5`` hardware type. To leverage this feature, the 'proliantutils'
library needs to be upgraded to version '2.10.0'.
- The ``one_button_secure_erase`` clean step in the ``ilo5`` hardware type
requires ``proliantutils`` version ``2.10.0``. Please upgrade this library
to leverage this feature.

7
releasenotes/notes/no-heartbeat-retries-d6837684e7257249.yaml
View File

@ -1,6 +1,7 @@
---
fixes:
- |
Agent heartbeat implementation will no longer retry attempts to acquire
an exclusive lock. This is done to avoid several attempts to get a lock
in a busy environment with shorter heartbeat period.
Fixes an issue where agent heartbeats would be queued if a pre-existing
lock was being held for the node which performed a heartbeat operation.
The agent heartbeat implementation will no longer retry attempts to
acquire an exclusive lock.