diff options
15 files changed, 33 insertions, 34 deletions
diff --git a/releasenotes/notes/add-neutron-request-timeout-1f7372af81f14ddd.yaml b/releasenotes/notes/add-neutron-request-timeout-1f7372af81f14ddd.yaml index eca1df044..5d033f31f 100644 --- a/releasenotes/notes/add-neutron-request-timeout-1f7372af81f14ddd.yaml +++ b/releasenotes/notes/add-neutron-request-timeout-1f7372af81f14ddd.yaml @@ -1,8 +1,7 @@ --- fixes: - | - Fixes an issue that can occur in CI and in physical deployments where the - Networking Service performs a pre-flight operation which can exceed - the prior default for ``30`` seconds. The new default is ``45`` seconds, - and operators can tune the setting via the ``[neutron]request_timeout`` - setting. + Fixes an issue where the Networking Service performs a pre-flight operation + which can exceed the prior default for ``30`` seconds. The new default is + ``45`` seconds, and operators can tune the setting via the + ``[neutron]request_timeout`` setting. diff --git a/releasenotes/notes/add-protection-for-available-nodes-25f163d69782ef63.yaml b/releasenotes/notes/add-protection-for-available-nodes-25f163d69782ef63.yaml index 23ff1da95..e41e2840a 100644 --- a/releasenotes/notes/add-protection-for-available-nodes-25f163d69782ef63.yaml +++ b/releasenotes/notes/add-protection-for-available-nodes-25f163d69782ef63.yaml @@ -1,12 +1,12 @@ --- features: - - Adds option 'allow_deleting_available_nodes' to control whether nodes in - state 'available' should be deletable (which is and stays the default). - Setting this option to False will remove 'available' from the list of + - Adds option ``allow_deleting_available_nodes`` to control whether nodes in + state ``available`` should be deletable (which is and stays the default). + Setting this option to ``False`` will remove ``available`` from the list of states in which nodes can be deleted from ironic. It hence provides protection against accidental removal of nodes which are ready for allocation (and is meant as a safeguard for the operational effort to bring nodes into this state). For backwards compatibility reasons, the - default value for this option is True. The other states in which nodes - can be deleted from ironic ('manageable', 'enroll', and 'adoptfail') + default value for this option is ``True``. The other states in which nodes + can be deleted from ironic (``manageable``, ``enroll``, and ``adoptfail``) remain unchanged. This option can be changed without service restart. diff --git a/releasenotes/notes/add-realtime-support-d814d5917836e9e2.yaml b/releasenotes/notes/add-realtime-support-d814d5917836e9e2.yaml index a6774c445..b24f12067 100644 --- a/releasenotes/notes/add-realtime-support-d814d5917836e9e2.yaml +++ b/releasenotes/notes/add-realtime-support-d814d5917836e9e2.yaml @@ -9,4 +9,5 @@ features: upgrade: - | - This change requires python-dracclient version 3.0.0 and later. + Updates the minimum required version of ``python-dracclient`` to ``3.0.0`` + when using the ``idrac`` hardware type. diff --git a/releasenotes/notes/allow-allocation-update-94d862c3da454be2.yaml b/releasenotes/notes/allow-allocation-update-94d862c3da454be2.yaml index 0c8d8d2bb..61afc8957 100644 --- a/releasenotes/notes/allow-allocation-update-94d862c3da454be2.yaml +++ b/releasenotes/notes/allow-allocation-update-94d862c3da454be2.yaml @@ -1,5 +1,5 @@ --- features: - | - Adds REST API endpoint for updating an existing allocation. Only ``name`` - and ``extra`` fields are allowed to be updated. + API version 1.57 adds a REST API endpoint for updating an existing + allocation. Only ``name`` and ``extra`` fields are allowed to be updated. diff --git a/releasenotes/notes/bug-2005377-5c63357681a465ec.yaml b/releasenotes/notes/bug-2005377-5c63357681a465ec.yaml index d610cfc37..4876b320c 100644 --- a/releasenotes/notes/bug-2005377-5c63357681a465ec.yaml +++ b/releasenotes/notes/bug-2005377-5c63357681a465ec.yaml @@ -1,6 +1,7 @@ --- fixes: - - Fixes node last_error and maintenance_reason overflow with too long error - messages, preventing the object from being correctly committed to database. - The maximum message length can be customized through a new configuration - parameter, ``[DEFAULT]/log_in_db_max_size`` (default, 4096 characters). + - Fixes overflowing of the node fields ``last_error`` and + ``maintenance_reason``, which would prevent the object from being correctly + committed to the database. The maximum message length can be customized + through a new configuration parameter, ``[DEFAULT]/log_in_db_max_size`` + (default, 4096 characters). diff --git a/releasenotes/notes/bug-2005764-15f45e11b9f9c96d.yaml b/releasenotes/notes/bug-2005764-15f45e11b9f9c96d.yaml index a6704e215..36947653c 100644 --- a/releasenotes/notes/bug-2005764-15f45e11b9f9c96d.yaml +++ b/releasenotes/notes/bug-2005764-15f45e11b9f9c96d.yaml @@ -1,8 +1,8 @@ --- fixes: - | - Fixes a deployment issue encountered during deployment, more precisely + Fixes an issue encountered during deployment, more precisely during the configdrive partition creation step. On some specific devices like NVMe drives, the created configdrive partition could not be correctly identified (required to dump data onto it afterward). - https://storyboard.openstack.org/#!/story/2005764 + See `story 2005764 <https://storyboard.openstack.org/#!/story/2005764>`_. diff --git a/releasenotes/notes/bug-30315-e46eafe5b575f3da.yaml b/releasenotes/notes/bug-30315-e46eafe5b575f3da.yaml index 52020517c..b9686c447 100644 --- a/releasenotes/notes/bug-30315-e46eafe5b575f3da.yaml +++ b/releasenotes/notes/bug-30315-e46eafe5b575f3da.yaml @@ -1,7 +1,7 @@ --- fixes: - | - Fixes an issue regarding the ``ansible deployment interface`` cleaning + Fixes an issue regarding the ``ansible`` deploy interface cleaning workflow. Handling the error in the driver and returning nothing caused the manager to consider the step done and go to the next one instead of interrupting diff --git a/releasenotes/notes/bug-30316-8c53358681e464eb.yaml b/releasenotes/notes/bug-30316-8c53358681e464eb.yaml index a992fbb53..acb7a7f4f 100644 --- a/releasenotes/notes/bug-30316-8c53358681e464eb.yaml +++ b/releasenotes/notes/bug-30316-8c53358681e464eb.yaml @@ -1,4 +1,4 @@ --- fixes: - - Fixes an issue with the ansible deployment interface where raw images + - Fixes an issue with the ``ansible`` deploy interface where raw images could not be streamed correctly to the host. diff --git a/releasenotes/notes/bug-30317-a972c8d879c98941.yaml b/releasenotes/notes/bug-30317-a972c8d879c98941.yaml index 793a5dc44..25fc5a5b7 100644 --- a/releasenotes/notes/bug-30317-a972c8d879c98941.yaml +++ b/releasenotes/notes/bug-30317-a972c8d879c98941.yaml @@ -1,5 +1,5 @@ --- fixes: - | - Fixes deployment with the ``ansible`` deploy interface and instance images with GPT partition - table. + Fixes deployment with the ``ansible`` deploy interface and instance images + with GPT partition table. diff --git a/releasenotes/notes/idrac-remove-commit_required-d9ea849e8f5e78e2.yaml b/releasenotes/notes/idrac-remove-commit_required-d9ea849e8f5e78e2.yaml index d735dfe98..0adf585a7 100644 --- a/releasenotes/notes/idrac-remove-commit_required-d9ea849e8f5e78e2.yaml +++ b/releasenotes/notes/idrac-remove-commit_required-d9ea849e8f5e78e2.yaml @@ -1,7 +1,7 @@ --- upgrade: - | - ``commit_required`` is no longer present in the dictionary returned by + Removes ``commit_required`` from the dictionary returned by the ``set_bios_config`` vendor passthru call in the ``idrac`` hardware type. ``commit_required`` was split into two keys: ``is_commit_required`` and ``is_reboot_required``, which indicate the actions necessary to diff --git a/releasenotes/notes/mdns-a5f4034257139e31.yaml b/releasenotes/notes/mdns-a5f4034257139e31.yaml index 8bb4327e7..6aeccdff6 100644 --- a/releasenotes/notes/mdns-a5f4034257139e31.yaml +++ b/releasenotes/notes/mdns-a5f4034257139e31.yaml @@ -1,6 +1,6 @@ --- features: - | - A new option ``enable_mdns`` allows to enable publishing the baremetal + Adds a new option ``enable_mdns`` which enables publishing the baremetal API endpoint via mDNS as specified in the `API SIG guideline <http://specs.openstack.org/openstack/api-sig/guidelines/dns-sd.html>`_. diff --git a/releasenotes/notes/remove-deprecated-hash_distribution_replicas-08351358eba4c9e1.yaml b/releasenotes/notes/remove-deprecated-hash_distribution_replicas-08351358eba4c9e1.yaml index 9ce421b57..a9087a4b9 100644 --- a/releasenotes/notes/remove-deprecated-hash_distribution_replicas-08351358eba4c9e1.yaml +++ b/releasenotes/notes/remove-deprecated-hash_distribution_replicas-08351358eba4c9e1.yaml @@ -1,6 +1,5 @@ --- upgrade: - | - The configuration option ``[DEFAULT]/hash_distribution_replicas`` was - deprecated in the Stein cycle. It has been removed - and is no longer supported. + Removes the configuration option ``[DEFAULT]/hash_distribution_replicas`` + which was deprecated in the Stein cycle. diff --git a/releasenotes/notes/remove-enabled-drivers-5afcd77b53da1499.yaml b/releasenotes/notes/remove-enabled-drivers-5afcd77b53da1499.yaml index 12da3bf44..37b24b226 100644 --- a/releasenotes/notes/remove-enabled-drivers-5afcd77b53da1499.yaml +++ b/releasenotes/notes/remove-enabled-drivers-5afcd77b53da1499.yaml @@ -1,7 +1,7 @@ --- upgrade: - | - The configuration option ``[DEFAULT]enabled_drivers`` is removed. The + Removes the configuration option ``[DEFAULT]enabled_drivers``. The option was deprecated in Rocky, and setting this option has raised an exception preventing conductor from starting since then. - ``[DEFAULT]enabled_hardware_types`` should be used instead.
\ No newline at end of file + ``[DEFAULT]enabled_hardware_types`` should be used instead. diff --git a/releasenotes/notes/send-sensor-data-for-all-nodes-a732d9df43e74318.yaml b/releasenotes/notes/send-sensor-data-for-all-nodes-a732d9df43e74318.yaml index a55c43b53..f35287bd9 100644 --- a/releasenotes/notes/send-sensor-data-for-all-nodes-a732d9df43e74318.yaml +++ b/releasenotes/notes/send-sensor-data-for-all-nodes-a732d9df43e74318.yaml @@ -7,7 +7,7 @@ features: is not enabled which aligns with the prior behavior of sensor data collection and transmission where such data was only collected if an ``instance_uuid`` was present to signify that the node has been or - is being deployed. With this change set to ``True``, operators may be able + is being deployed. With this option set to ``True``, operators may be able to identify hardware in a faulty state through the sensor data and take action before an instance workload is deployed. fixes: diff --git a/releasenotes/notes/use-ironic-lib-exception-4bff237c9667bf46.yaml b/releasenotes/notes/use-ironic-lib-exception-4bff237c9667bf46.yaml index 9a6f8c2ea..02400d534 100644 --- a/releasenotes/notes/use-ironic-lib-exception-4bff237c9667bf46.yaml +++ b/releasenotes/notes/use-ironic-lib-exception-4bff237c9667bf46.yaml @@ -4,6 +4,5 @@ deprecations: deprecated. Please use the configuration option ``[ironic_lib]/fatal_exception_format_errors`` instead. -other: - - Use the module exception from ironic-lib. - Update ironic-lib minimum version required to 2.17.1. +upgrade: + - Updates the minimum required version of ``ironic-lib`` to ``2.17.1``. |