Prepare for bugfix release

Change-Id: I8b4900831bd4828f61926c92d4c53f818a8a087a
This commit is contained in:
Riccardo Pittau 2021-12-06 12:46:11 +01:00
parent e51c6b930e
commit 5f35896bfb
8 changed files with 34 additions and 31 deletions

View File

@ -1,9 +1,9 @@
--- ---
features: features:
- | - |
Adding support for running ``management.clear_job_queue``, Adds support for running ``management.clear_job_queue``,
``management.reset_idrac`` and ``management.known_good_state`` methods as ``management.reset_idrac`` and ``management.known_good_state`` methods as
verify steps on iDRAC hardware type, for both ``idrac-wsman`` and verify steps on iDRAC hardware type, for both ``idrac-wsman`` and
``idrac-redfish`` interfaces. In order to use this feature, ``idrac-redfish`` interfaces. In order to use this feature,
``[conductor]verify_step_priority_override`` needs to be used to set ``[conductor]verify_step_priority_override`` needs to be used to set
non-zero step priorties for the desired verify steps. non-zero step priorities for the desired verify steps.

View File

@ -1,25 +1,25 @@
--- ---
fixes: fixes:
- | - |
Fixes a bug in the anaconda deploy interface where the 'ks_options' Fixes a bug in the anaconda deploy interface where the ``ks_options``
key was not found when rendering the default kickstart template. key was not found when rendering the default kickstart template.
- | - |
Fixes issue where PXEAnacondaDeploy interface's deploy() method did not Fixes an issue where PXEAnacondaDeploy interface's deploy() method did not
return states.DEPLOYWAIT so the instance went straight to 'active' instead return states.DEPLOYWAIT so the instance went straight to ``active`` instead
of 'wait call-back'. of ``wait call-back``.
- | - |
Fixes an issue where the anaconda deploy interface mistakenly expected Fixes an issue where the anaconda deploy interface mistakenly expected
'squashfs_id' instead of 'stage2_id' property on the image. ``squashfs_id`` instead of ``stage2_id`` property on the image.
- | - |
Fixes the heartbeat mechanism in the default kickstart template Fixes the heartbeat mechanism in the default kickstart template
ks.cfg.template as the heartbeat API only accepts 'POST' and expects a ks.cfg.template as the heartbeat API only accepts ``POST`` and expects a
mandatory 'callback_url' parameter. mandatory ``callback_url`` parameter.
- | - |
Fixes handling of tarball images in anaconda deploy interface. Allows user Fixes handling of tarball images in anaconda deploy interface. Allows user
specified file extensions to be appended to the disk image symlink. Users specified file extensions to be appended to the disk image symlink. Users
can now set the file extensions by setting the 'disk_file_extension' can now set the file extensions by setting the ``disk_file_extension``
property on the OS image. This enables users to deploy tarballs with property on the OS image. This enables users to deploy tarballs with
anaconda deploy interface. anaconda deploy interface.
- | - |
Fixes issue where automated cleaning was not supported when anaconda deploy Fixes an issue where automated cleaning was not supported when anaconda
interface is used. deploy interface is used.

View File

@ -2,11 +2,15 @@
fixes: fixes:
- | - |
Fixes ``idrac-wsman`` management interface ``set_boot_device`` method that Fixes ``idrac-wsman`` management interface ``set_boot_device`` method that
would fail deployment when there are existing jobs present with error would fail deployment when there are existing jobs present with
"Failed to change power state to ''power on'' by ''rebooting''. Error: DRAC the error::
operation failed. Reason: Unfinished config jobs found: <list of existing
jobs>. Make sure they are completed before retrying.". Now there can be "Failed to change power state to ''power on'' by ''rebooting''.
non-BIOS jobs present during deployment. This will still fail for cases Error: DRAC operation failed. Reason: Unfinished config jobs
when there are BIOS jobs present. In such cases should consider moving to found: <list of existing jobs>. Make sure they are completed
``idrac-redfish`` that does not have this limitation when setting boot before retrying."
device.
Now there can be non-BIOS jobs present during deployment.
This will still fail for cases when there are BIOS jobs present.
In such cases it's advised to use the ``idrac-redfish`` interface
that does not have this limitation when setting boot device.

View File

@ -1,7 +1,7 @@
--- ---
fixes: fixes:
- | - |
Fixes issue with a node's instance_info interface override caused when Fixes an issue with a node's instance_info interface override caused when
Ironic uses the interface attribute directly. Does so by adding a Ironic uses the interface attribute directly. Does so by adding a
`get_interface` method to a node, and updating the Ironic code to use it ``get_interface`` method to a node, and updating the Ironic code to use
where needed. it where needed.

View File

@ -1,5 +1,5 @@
--- ---
fixes: fixes:
- | - |
Fix the bug caused by not converting the port value to int type Fixes an issue where the port value is not converted to int type
when the node managed by the `irmc` hardware type. when nodes are managed by the ``irmc`` hardware type.

View File

@ -1,7 +1,6 @@
--- ---
fixes: fixes:
- | - |
Fixed the bug of repeated resume cleaning due to the value of Fixes an issue where cleaning continuously repeats due to the value of
`fgi_status` not being updated correctly when obtaining the ``fgi_status`` not being updated correctly when obtaining the RAID
RAID configuration status of the node managed by the `irmc` configuration status of nodes managed by the ``irmc`` hardware type.
hardware type.

View File

@ -2,6 +2,6 @@
features: features:
- | - |
ISO images provided via ``instance_info/boot_iso`` or ISO images provided via ``instance_info/boot_iso`` or
`instance_info/deploy_iso`` are now cached in a similar way to normal ``instance_info/deploy_iso`` are now cached in a similar way to normal
instance images. Set ``[deploy]iso_master_path`` to an empty string instance images. Set ``[deploy]iso_master_path`` to an empty string
to disable. to disable.

View File

@ -6,7 +6,7 @@ features:
set their nodes, or deployment, appropriately. set their nodes, or deployment, appropriately.
upgrade: upgrade:
- | - |
The default boot mode has been changed and now UEFI. Operators who The default boot mode has been changed and is *now* UEFI. Operators who
were explicitly relying upon BIOS based deployments in the past, were explicitly relying upon BIOS based deployments in the past,
may wish to consider setting an explicit node level override for may wish to consider setting an explicit node level override for
the node to only utilize BIOS mode. This can be configured at a the node to only utilize BIOS mode. This can be configured at a