diff --git a/releasenotes/notes/add_retirement_support-23c5fed7ce8f97d4.yaml b/releasenotes/notes/add_retirement_support-23c5fed7ce8f97d4.yaml index 8165df1d9a..82a30020df 100644 --- a/releasenotes/notes/add_retirement_support-23c5fed7ce8f97d4.yaml +++ b/releasenotes/notes/add_retirement_support-23c5fed7ce8f97d4.yaml @@ -3,7 +3,7 @@ features: - | Adds support for node retirement by adding a ``retired`` property to the node. If set, a node moves upon automatic cleaning to - ``manageable`` (rather than ``available``). The new property can also - block the provide keyword, i.e. nodes cannot move from ``manageable`` - to ``available``. Furthermore, there is an additional optional property - ``retirement_reason`` to store the reason for the node's retirement. \ No newline at end of file + ``manageable`` (rather than ``available``). The new property also + blocks the ``provide`` keyword, i.e. nodes cannot move from ``manageable`` + to ``available``. Furthermore, there is an additional optional field + ``retirement_reason`` to store the reason for the node's retirement. diff --git a/releasenotes/notes/ansible-loops-de0eef0d5b79a9ff.yaml b/releasenotes/notes/ansible-loops-de0eef0d5b79a9ff.yaml index 85f9a4085b..eb6508cdcc 100644 --- a/releasenotes/notes/ansible-loops-de0eef0d5b79a9ff.yaml +++ b/releasenotes/notes/ansible-loops-de0eef0d5b79a9ff.yaml @@ -1,5 +1,5 @@ --- upgrade: - | - Changing minimum version of Ansible for use with the ``ansible`` + Changes the minimum version of Ansible for use with the ``ansible`` ``deploy_interface`` to version 2.5. diff --git a/releasenotes/notes/configdrive-vendordata-122049bd7c6e1b67.yaml b/releasenotes/notes/configdrive-vendordata-122049bd7c6e1b67.yaml index 4334e3a8fd..ee79c50e50 100644 --- a/releasenotes/notes/configdrive-vendordata-122049bd7c6e1b67.yaml +++ b/releasenotes/notes/configdrive-vendordata-122049bd7c6e1b67.yaml @@ -3,6 +3,6 @@ features: - | Adds support for specifying vendor_data when building config drives. Starting with API version 1.59, a JSON based ``configdrive`` parameter to - ``/v1/nodes//states/provision`` can include the key vendor_data. + ``/v1/nodes//states/provision`` can include the key ``vendor_data``. This data will be built into the configdrive contents as - vendor_data2.json. \ No newline at end of file + ``vendor_data2.json``. diff --git a/releasenotes/notes/fix-commit-to-controller-d26f083ac388a65e.yaml b/releasenotes/notes/fix-commit-to-controller-d26f083ac388a65e.yaml index 7a37efd32c..3dea631920 100644 --- a/releasenotes/notes/fix-commit-to-controller-d26f083ac388a65e.yaml +++ b/releasenotes/notes/fix-commit-to-controller-d26f083ac388a65e.yaml @@ -4,5 +4,5 @@ fixes: for RAID ``delete_configuration`` cleaning step gets created even when there are no virtual disks or hotspares/dedicated hotspares present on any controller. - See bug `2006562 https://storyboard.openstack.org/#!/story/2006562` + See bug `2006562 `_ for details. diff --git a/releasenotes/notes/fix-delete_configuration-with-multiple-controllers-06fc3fca94ba870f.yaml b/releasenotes/notes/fix-delete_configuration-with-multiple-controllers-06fc3fca94ba870f.yaml index 38c637df4c..a24f89d896 100644 --- a/releasenotes/notes/fix-delete_configuration-with-multiple-controllers-06fc3fca94ba870f.yaml +++ b/releasenotes/notes/fix-delete_configuration-with-multiple-controllers-06fc3fca94ba870f.yaml @@ -5,5 +5,5 @@ fixes: realtime mode and some do not. The approach is to use only realtime mode if all controllers support realtime. This removes the race condition. - See bug `2006502 https://storyboard.openstack.org/#!/story/2006502` - for details + See bug `2006502 `_ + for details. diff --git a/releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml b/releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml index dc10ea8c2b..51d6c09b77 100644 --- a/releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml +++ b/releasenotes/notes/fix-fields-missing-from-next-url-fd9fddf8e70b65ea.yaml @@ -2,7 +2,7 @@ fixes: - | Fixes issue where the resource list API returned results with requested - fields only until the API MAX_LIMIT. After the API MAX_LIMIT is reached the - API started ignoring user requested fields. This fix will make sure that - the next url generated by the pagination code will include the user - requested fields as query parameter. + fields only until the API ``MAX_LIMIT``. After the API ``MAX_LIMIT`` is + reached the API started ignoring user requested fields. This fix will make + sure that the next url generated by the pagination code will include the + user requested fields as query parameter. diff --git a/releasenotes/notes/fix-path-a3a0cfd2c135ace9.yaml b/releasenotes/notes/fix-path-a3a0cfd2c135ace9.yaml index 1f524bca07..4f40959e9b 100644 --- a/releasenotes/notes/fix-path-a3a0cfd2c135ace9.yaml +++ b/releasenotes/notes/fix-path-a3a0cfd2c135ace9.yaml @@ -1,5 +1,5 @@ --- fixes: - | - Fix path used to virtual media iso, when served over - local HTTP server([redfish]use_swift=false). + Fixes virtual media boot when served using a local HTTP server, + i.e. ``[redfish]use_swift`` is ``false``. diff --git a/releasenotes/notes/fix_pending_non_bios_job_execution-4b22e168ac915f4f.yaml b/releasenotes/notes/fix_pending_non_bios_job_execution-4b22e168ac915f4f.yaml index 1722c263e6..0a65662b34 100644 --- a/releasenotes/notes/fix_pending_non_bios_job_execution-4b22e168ac915f4f.yaml +++ b/releasenotes/notes/fix_pending_non_bios_job_execution-4b22e168ac915f4f.yaml @@ -6,5 +6,5 @@ fixes: (E.g. create/delete virtual disk) were not being deleted before job execution. - See bug `2006580 https://storyboard.openstack.org/#!/story/2006580` - for details + See bug `2006580 `_ + for details. diff --git a/releasenotes/notes/no-localhost-596adedfe388dfae.yaml b/releasenotes/notes/no-localhost-596adedfe388dfae.yaml deleted file mode 100644 index 5e56962811..0000000000 --- a/releasenotes/notes/no-localhost-596adedfe388dfae.yaml +++ /dev/null @@ -1,7 +0,0 @@ ---- -upgrade: - - | - Using localhost as the Bare Metal Introspection endpoint will not work - when managed boot is used for in-band inspection. Either update the - endpoint to a real IP address or use the new configuration option - ``[inspector]callback_endpoint_override``. diff --git a/releasenotes/notes/node-owner-policy-d7168976bba70566.yaml b/releasenotes/notes/node-owner-policy-d7168976bba70566.yaml index 0958eb047c..97e629d8db 100644 --- a/releasenotes/notes/node-owner-policy-d7168976bba70566.yaml +++ b/releasenotes/notes/node-owner-policy-d7168976bba70566.yaml @@ -1,6 +1,6 @@ --- features: - - Adds a ``is_node_owner`` policy rule. This rule can be used with node + - Adds an ``is_node_owner`` policy rule. This rule can be used with node policy rules in order to expose specific node APIs to a project ID specified by a node's ``owner`` field. Default rules are unaffected, so default behavior is unchanged. diff --git a/releasenotes/notes/ramdisk-params-6083bfaa7ffa9dfe.yaml b/releasenotes/notes/ramdisk-params-6083bfaa7ffa9dfe.yaml index f0c816974c..dbdf4393e3 100644 --- a/releasenotes/notes/ramdisk-params-6083bfaa7ffa9dfe.yaml +++ b/releasenotes/notes/ramdisk-params-6083bfaa7ffa9dfe.yaml @@ -1,6 +1,6 @@ --- upgrade: - | - The operators using custom PXE/iPXE/Grub templates should update them to + Operators using custom PXE/iPXE/Grub templates should update them to remove an explicit mention of ``ipa-api-url``. This field is now a part of ``pxe_append_params`` when required. diff --git a/releasenotes/notes/sofware_raid_use_rootfs_uuid-f61eb671d696d251.yaml b/releasenotes/notes/sofware_raid_use_rootfs_uuid-f61eb671d696d251.yaml index 25495dee80..732e3777a9 100644 --- a/releasenotes/notes/sofware_raid_use_rootfs_uuid-f61eb671d696d251.yaml +++ b/releasenotes/notes/sofware_raid_use_rootfs_uuid-f61eb671d696d251.yaml @@ -9,5 +9,5 @@ upgrade: of the deployed image is in the first partition. Instead, it will use the UUID passed from the conductor. Operators need hence to make sure that the conductor has the correct UUID (which either comes from the - 'rootfs_uuid' field in the image metadata or from the - 'root_uuid_or_disk_id' in the nodes 'internal_driver_info'.) + ``rootfs_uuid`` field in the image metadata or from the + ``root_uuid_or_disk_id`` in the node's ``internal_driver_info``.)