ced328ca18
We have used the dns_nameservers from the subnets for
a long time by default: https://review.opendev.org/579582
With network config being applied prior to creating the heat
stack we cannot use a THT parameter to feed the input for
node network configuration. In Wallaby and later the nameservers
must be defined in undercloud.conf using:
'DEFAULT/undercloud_nameservers'
or
'%SUBNET_SECTION%/dns_nameservers'
The latter allow defining nameservers per-ctlplane subnet.
Related: RHBZ#2068489
Change-Id: I436fa7f1e87a8e6924c9d93105b06f9ab39eeb8f
(cherry picked from commit 42506f635d
)
16 lines
587 B
YAML
16 lines
587 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The tripleo-heat-templates parameter DnsServers has been deprecated.
|
|
|
|
The dns_nameservers from the ctlplane subnets has been used by default for
|
|
overcloud node nameservers for a long time, see:
|
|
https://review.opendev.org/579582.
|
|
|
|
Since Wallaby network configuration is applied prior to the Heat stack
|
|
create, during overcloud node provisioning. In this case the THT parameter
|
|
DnsServers is not available when network configuration is applied.
|
|
Effectively the DnsServers parameter cannot be used in Wallaby and later
|
|
releases.
|
|
|