v1 network render to netplan does not render IPv6 global nameserver address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Low
|
Unassigned |
Bug Description
cloud-init v 22.2:
Example config with subnet `type: ipv6_slaac` doesn't render any nameserver information in config /etc/netplan/
Steps to reproduce:
cat > network-config <<EOF
version: 1
config:
- type: physical
name: eth0
mac_address: '06:70:c5:13:04:1e'
subnets:
- type: ipv6_slaac
- type: nameserver
address:
- '2a03:7900:
search:
- 'demo.de'
EOF
PYTHONPATH=. python3 -m cloudinit.cmd.main devel net-convert --network-
# ACTUAL OUTPUT - lacks nameserver
$ cat outputd/
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp6: true
match:
It may be that this isn't a bug because ipv6_slaac doesn't provide DNS information and requires that the a separate https:/
Currently cloud-init netplan renderer only applies global nameserfver information to subnets which contain an "addresses" config directive an no nameserver" directive.
https:/
summary: |
- v1 network render to netplan does not render IPv6 nameserver address + v1 network render to netplan does not render ipv6_slaac nameserver + address |
For this particular issue: I believe adding a dns_nameservers: ['2a03: 7900:2: 0:31:3: 104:161' ] to eth0's subnets definition will get you want you overriding default behavior.