Fix regression of Nova dhcp_domain handling
As of https://review.opendev.org/774415
nova::metadata::dhcp_domain values in custom hiera
overrides stopped working for users.
As a result, during updates/upgrades, that might alter
existing hostnames for Nova compute nodes.
Fix regression by honoring legacy nova::metadata::dhcp_domain
alongside nova::dhcp_domain values.
Change-Id: I4889600be9f31532ac30d944bde28a64cff5ed26
Related: rhbz#2181566
Co-authored-by: Takashi Kajinami <tkajinam@redhat.com>
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
(cherry picked from commit 0d5139ee56
)
This commit is contained in:
parent
68b4a7c87d
commit
e60b46efd7
@ -171,6 +171,7 @@ class tripleo::profile::base::nova (
|
||||
'password' => $oslomsg_notify_password,
|
||||
'ssl' => $oslomsg_notify_use_ssl_real,
|
||||
}),
|
||||
dhcp_domain => hiera('nova::metadata::dhcp_domain', hiera('nova::dhcp_domain', '')),
|
||||
}
|
||||
include ::nova::placement
|
||||
include ::nova::keystone::service_user
|
||||
|
Loading…
Reference in New Issue
Block a user