diff options
Diffstat (limited to 'releasenotes')
10 files changed, 84 insertions, 8 deletions
diff --git a/releasenotes/notes/ValueDisplayName-13837c653277ff08.yaml b/releasenotes/notes/ValueDisplayName-13837c653277ff08.yaml new file mode 100644 index 000000000..6abac74c6 --- /dev/null +++ b/releasenotes/notes/ValueDisplayName-13837c653277ff08.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixes detecting of allowable values for a BIOS settings enumeration in + the ``redfish`` BIOS interface when only ``ValueDisplayName`` is provided. diff --git a/releasenotes/notes/deprecate-syslinux-support-98d327c67607fc8e.yaml b/releasenotes/notes/deprecate-syslinux-support-98d327c67607fc8e.yaml index 670047a82..9543f9d84 100644 --- a/releasenotes/notes/deprecate-syslinux-support-98d327c67607fc8e.yaml +++ b/releasenotes/notes/deprecate-syslinux-support-98d327c67607fc8e.yaml @@ -23,4 +23,4 @@ deprecations: - Deprecation of ``pxelinux``, as a result of the deprecation of ``syslinux``, does ultimately mean the default for the ``pxe`` boot_interface to carry defaults for the use of grub based network booting, specifically for - for operators who are unable to use iPXE. + operators who are unable to use iPXE. diff --git a/releasenotes/notes/fast-track-bios-fa9ae685c151dd24.yaml b/releasenotes/notes/fast-track-bios-fa9ae685c151dd24.yaml new file mode 100644 index 000000000..b4a8004f7 --- /dev/null +++ b/releasenotes/notes/fast-track-bios-fa9ae685c151dd24.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - | + Fixes rebooting into the agent after changing BIOS settings in fast-track + mode with the ``redfish-virtual-media`` boot interface. Previously, the ISO + would not be configured. diff --git a/releasenotes/notes/fix-ilo-boot-interface-order-238a2da9933cf28c.yaml b/releasenotes/notes/fix-ilo-boot-interface-order-238a2da9933cf28c.yaml new file mode 100644 index 000000000..586ea6b82 --- /dev/null +++ b/releasenotes/notes/fix-ilo-boot-interface-order-238a2da9933cf28c.yaml @@ -0,0 +1,26 @@ +--- +fixes: + - | + Fixes the default boot interface order for the ``ilo`` hardware type + where previously it would prefer ``pxe`` over ``ipxe``. This created + inconsistencies for operators using multiple hardware types, where + both interfaces were enabled in the deployment. +upgrade: + - | + Operators who are upgrading should be aware that a bug was discovered + with the automatic selection of ``boot_interface`` for users of the + ``ilo`` and ``ilo5`` hardware types. This was an inconsistency, + resulting in ``pxe`` being selected instead of ``ipxe`` if both + boot interfaces were enabled. Depending on the local configuration, + this may, or may not have happened and will remain static on + preexisting baremetal nodes. Some users may have been relying + upon this incorrect behavior by having misalligned defaults by trying + to use the ``pxe`` interface for ``ipxe``. Users wishing to continue + this usage as it was previously will need to explicitly set a + ``boot_interface`` value to either ``pxe`` or ``ilo-ipxe`` by default, + depending on the local configuration. Most operators have leveraged + the default examples, and thus did not explicitly encounter this + condition. Operators explicitly wishing to use ``pxe`` boot interfaces + with the ``ipxe`` templates and defaults set to override the defaults + for ``ironic.conf`` will need to either continue to leverage default + override configurations in their ``ironic.conf`` file. diff --git a/releasenotes/notes/fix-pxe-glance-lookup-anaconda-86fe616c6286ec08.yaml b/releasenotes/notes/fix-pxe-glance-lookup-anaconda-86fe616c6286ec08.yaml index bf6b8ea85..961b49cb0 100644 --- a/releasenotes/notes/fix-pxe-glance-lookup-anaconda-86fe616c6286ec08.yaml +++ b/releasenotes/notes/fix-pxe-glance-lookup-anaconda-86fe616c6286ec08.yaml @@ -2,5 +2,5 @@ fixes: - | Fixes an issue in the ``anaconda`` deployment interface where PXE argument - processing and preparation was erroniously directly connecting to Glance, + processing and preparation was erroneously directly connecting to Glance, potentially leading to an exception in the standalone use case. diff --git a/releasenotes/notes/jsonschema-4.8-1146d103b877cffd.yaml b/releasenotes/notes/jsonschema-4.8-1146d103b877cffd.yaml new file mode 100644 index 000000000..75c0a6c50 --- /dev/null +++ b/releasenotes/notes/jsonschema-4.8-1146d103b877cffd.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixes API error messages with jsonschema>=4.8. A possible root cause is + now detected for generic schema errors. diff --git a/releasenotes/notes/node-creation-no-longer-scope-restricted-b455f66a751f10ec.yaml b/releasenotes/notes/node-creation-no-longer-scope-restricted-b455f66a751f10ec.yaml new file mode 100644 index 000000000..b405dddb3 --- /dev/null +++ b/releasenotes/notes/node-creation-no-longer-scope-restricted-b455f66a751f10ec.yaml @@ -0,0 +1,27 @@ +--- +features: + - | + Adds the capability for a project scoped ``admin`` user to be able to + create nodes in Ironic, which are then manageable by the project scoped + ``admin`` user. Effectively, this is self service Bare Metal as a Service, + however more advanced fields such as drivers, chassies, are not available + to these users. This is controlled through an auto-population of the + Node ``owner`` field, and can be controlled through the + ``[api]project_admin_can_manage_own_nodes`` setting, which defaults to + ``True``, and the new policy ``baremetal:node:create:self_owned_node``. + - | + Adds the capability for a project scoped ``admin`` user to be able to + delete nodes from Ironic which their `project` owns. This can be + contolled through the ``[api]project_admin_can_manage_own_nodes`` + setting, which defaults to ``True``, as well as the + ``baremetal:node:delete:self_owned_node`` policy. +security: + - | + This release contains an improvement which, by default, allows users to + create and delete baremetal nodes inside their own project. This can be + disabled using the ``[api]project_admin_can_manage_own_nodes`` setting. +upgrades: + - | + The API version has been increased to ``1.80`` in order to signify + the addition of additoinal Role Based Access Controls capabilities + around node creation and deletion.
\ No newline at end of file diff --git a/releasenotes/notes/prevent-pxe-retry-when-token-exists-a4f38f7da56c1397.yaml b/releasenotes/notes/prevent-pxe-retry-when-token-exists-a4f38f7da56c1397.yaml index 5db6db6ec..62e7ae9ca 100644 --- a/releasenotes/notes/prevent-pxe-retry-when-token-exists-a4f38f7da56c1397.yaml +++ b/releasenotes/notes/prevent-pxe-retry-when-token-exists-a4f38f7da56c1397.yaml @@ -1,7 +1,7 @@ --- fixes: - | - Fixes a race condition in PXE initialization where logic to retry + Fixes a race condition in PXE initialization where the logic to retry what we suspect as potentially failed PXE boot operations was not consulting if an ``agent token`` had been established, which is the very first step in agent initialization. diff --git a/releasenotes/notes/redfish_consider_password_in_session_cache-1fa84234db179053.yaml b/releasenotes/notes/redfish_consider_password_in_session_cache-1fa84234db179053.yaml new file mode 100644 index 000000000..af48b88fa --- /dev/null +++ b/releasenotes/notes/redfish_consider_password_in_session_cache-1fa84234db179053.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + Fixes an issue where the Redfish session cache would continue using an + old session when a password for a Redfish BMC was changed. Now the old + session will not be found in this case, and a new session will be created + with the latest credential information available. diff --git a/releasenotes/notes/skip-clear-job-queue-idrac-reset-if-attr-missing-b2a2b609c906c6c4.yaml b/releasenotes/notes/skip-clear-job-queue-idrac-reset-if-attr-missing-b2a2b609c906c6c4.yaml index df9bef955..a829cbd97 100644 --- a/releasenotes/notes/skip-clear-job-queue-idrac-reset-if-attr-missing-b2a2b609c906c6c4.yaml +++ b/releasenotes/notes/skip-clear-job-queue-idrac-reset-if-attr-missing-b2a2b609c906c6c4.yaml @@ -1,8 +1,8 @@ --- fixes: - | - Resolved clear_job_queue and reset_idrac verify step failures which occur - when the functionality is not supported by the iDRAC. When this condition - is detected, the code in the step handles the exception and logs a warning - and completes successfully in case of verification steps but fails in case - of cleaning steps. + Resolved ``clear_job_queue`` and ``reset_idrac`` verify step failures which + occur when the functionality is not supported by the iDRAC. When this + condition is detected, the code in the step handles the exception and logs + a warning and completes successfully in case of verification steps but + fails in case of cleaning steps. |