diff --git a/releasenotes/notes/bug-1695861-ebc8a0aa7a87f7e0.yaml b/releasenotes/notes/bug-1695861-ebc8a0aa7a87f7e0.yaml index 57303608aa21..74e6cdbb4172 100644 --- a/releasenotes/notes/bug-1695861-ebc8a0aa7a87f7e0.yaml +++ b/releasenotes/notes/bug-1695861-ebc8a0aa7a87f7e0.yaml @@ -3,7 +3,7 @@ fixes: - | Fixes `bug 1695861`_ in which the aggregate API accepted requests that have availability zone names including ':'. With this fix, a creation - of an availabilty zone whose name includes ':' results in a + of an availability zone whose name includes ':' results in a ``400 BadRequest`` error response. .. _bug 1695861: https://bugs.launchpad.net/nova/+bug/1695861 diff --git a/releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml b/releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml index 72c6b7e56c93..bde6b9a49ebc 100644 --- a/releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml +++ b/releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml @@ -4,7 +4,7 @@ deprecations: The following nova-manage commands are deprecated for removal in the Nova 15.0.0 Ocata release: - * nova-maange account scrub + * nova-manage account scrub * nova-manage fixed * * nova-manage floating * * nova-manage network * diff --git a/releasenotes/notes/hyperv-uefi-secure-boot-a2a617ac2c313afd.yaml b/releasenotes/notes/hyperv-uefi-secure-boot-a2a617ac2c313afd.yaml index 72f738080989..f20e1d5d1a25 100644 --- a/releasenotes/notes/hyperv-uefi-secure-boot-a2a617ac2c313afd.yaml +++ b/releasenotes/notes/hyperv-uefi-secure-boot-a2a617ac2c313afd.yaml @@ -7,7 +7,7 @@ features: * Images should be prepared for Generation 2 VMs. The image property "hw_machine_type=hyperv-gen2" is mandatory. * The guest OS type must be specified in order to properly spawn the VMs. - It can be specifed through the image property "os_type", and the + It can be specified through the image property "os_type", and the acceptable values are "windows" or "linux". * The UEFI Secure Boot feature can be requested through the image property "os_secure_boot" (acceptable values: "disabled", "optional", "required") diff --git a/releasenotes/notes/instance-path-2efca507456d8a70.yaml b/releasenotes/notes/instance-path-2efca507456d8a70.yaml index e2f67962c1a5..ce9e64211fd9 100644 --- a/releasenotes/notes/instance-path-2efca507456d8a70.yaml +++ b/releasenotes/notes/instance-path-2efca507456d8a70.yaml @@ -9,6 +9,6 @@ upgrade: ``/opt/stack/data/nova/instances/34198248-5541-4d52-a0b4-a6635a7802dd/``. In Newton backward compatibility is dropped. For instances that haven't - been restarted since Folsom and earlier maintanance should be scheduled + been restarted since Folsom and earlier maintenance should be scheduled before upgrade(stop, rename directory to instance.uuid, then start) so Nova will start using new paths for instances. diff --git a/releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml b/releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml index efc996a62113..615d6100f08f 100644 --- a/releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml +++ b/releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml @@ -3,5 +3,5 @@ upgrade: - In mitaka, an online migration was added to migrate older SRIOV parent device information from extra_info to a new column. Since two releases have gone out with that migration, it is removed in Ocata and operators - are expetected to have run it as part of either of the previous two + are expected to have run it as part of either of the previous two releases, if applicable. diff --git a/releasenotes/notes/server_migrations-30519b35d3ea6763.yaml b/releasenotes/notes/server_migrations-30519b35d3ea6763.yaml index aa6feadc513b..3d7817578d64 100644 --- a/releasenotes/notes/server_migrations-30519b35d3ea6763.yaml +++ b/releasenotes/notes/server_migrations-30519b35d3ea6763.yaml @@ -2,7 +2,7 @@ features: - | Add two new list/show API for server-migration. - The list API will return the in progress live migratons + The list API will return the in progress live migrations information of a server. The show API will return a specified in progress live migration of a server. This has been added in microversion 2.23. diff --git a/releasenotes/notes/validate-expired-user-tokens-57a265cb4ee4ba6f.yaml b/releasenotes/notes/validate-expired-user-tokens-57a265cb4ee4ba6f.yaml index 4701dd201e74..5f0c5b75e32b 100644 --- a/releasenotes/notes/validate-expired-user-tokens-57a265cb4ee4ba6f.yaml +++ b/releasenotes/notes/validate-expired-user-tokens-57a265cb4ee4ba6f.yaml @@ -8,7 +8,7 @@ features: has expired. In order to use this functionality a service user needs to be created. Add service user configurations in ``nova.conf`` under ``service_user`` group and set ``send_service_user_token`` flag to - ``True``. The minimum Keytone API version 3.8 and Keystone middleware + ``True``. The minimum Keystone API version 3.8 and Keystone middleware version 4.12.0 is required to use this functionality. This only currently works with Nova - Cinder and Nova - Neutron API interactions.