undercloud subnet dns_nameservers option default overrides undercloud_nameservers in global conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
High
|
Harald Jensås |
Bug Description
Using 'undercloud_
Related Infrared change: https:/
UPDATE:
constants.
This is the default for [ctlplane-
Code[1] - should set 'undercloud_
if s.get('
else:
It is possible this worked in CI because of this script that removed test coverage in CI executes:
https:/
Changed in tripleo: | |
status: | Triaged → Incomplete |
description: | updated |
Changed in tripleo: | |
importance: | Undecided → High |
description: | updated |
Changed in tripleo: | |
status: | Incomplete → Invalid |
We have unit test coverage that show's that setting the subnets dns_nameserver = [] and undercloud_ nameservers = ['10.10.10.10', '10.10.10.11'] set 'DnsNameServers': ['10.10.10.10', '10.10.10.11'].
https:/ /opendev. org/openstack/ python- tripleoclient/ src/branch/ master/ tripleoclient/ tests/v1/ undercloud/ test_config. py#L129 /opendev. org/openstack/ python- tripleoclient/ src/branch/ master/ tripleoclient/ tests/v1/ undercloud/ test_config. py#L175
https:/
The reporter tell me overcloud nodes got 192.168.24.5 as nameserver. constants. CTLPLANE_ DHCP_START_ DEFAULT = ['192.168.24.5'], if no nameserver is specified when creating the subnet neutron probably default to the IP address of the dhcp agent's dnsmasq which is the first address of the allocation pool.
The reporter assure's me that undercloud_ nameservers = 10.10.160.1 is set in undercloud.conf.