On multi-region deployments, Nova may talk to the wrong
neutron endpoint (from the wrong region) if the region
is unspecified.
On Rocky+ it will also require updating the
os_region_name config to region_name, as os_region_name
has been deprecated, otherwise Nova will talk to the wrong
placement endpoint as well.
This fix addresses the issue where nova-compute will not
register the node to the correct nova_api/placement
database, and will also not be able to complete live-migrations.
Given that the template for the [placement] section is
applied to every release, it is included both old and
new config options.
Change-Id: I9500ba400d55e6f1bc11f2ba05b25b4714cda578
Closes-bug: #1903210
(cherry picked from commit 835d4b167ab7db41962239eaabb56f492fa34cde)
Reviewed: https:/ /review. opendev. org/762153 /opendev. org/openstack/ charm-nova- compute/ commit/ 7a178053f1cb915 f3fe50f328c7a2c f90c03f565
Committed: https:/
Submitter: Zuul
Branch: stable/20.10
commit 7a178053f1cb915 f3fe50f328c7a2c f90c03f565
Author: Rodrigo Barbieri <email address hidden>
Date: Thu Nov 5 18:32:10 2020 -0300
Add/update region config in nova.conf
On multi-region deployments, Nova may talk to the wrong
neutron endpoint (from the wrong region) if the region
is unspecified.
On Rocky+ it will also require updating the
os_region_name config to region_name, as os_region_name
has been deprecated, otherwise Nova will talk to the wrong
placement endpoint as well.
This fix addresses the issue where nova-compute will not
register the node to the correct nova_api/placement
database, and will also not be able to complete live-migrations.
Given that the template for the [placement] section is
applied to every release, it is included both old and
new config options.
Change-Id: I9500ba400d55e6 f1bc11f2ba05b25 b4714cda578 1962239eaabb56f 492fa34cde)
Closes-bug: #1903210
(cherry picked from commit 835d4b167ab7db4