dns-search rendered for ipv4 when no addresses configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Users configuring IPv6 static address with NetworkManager as a backend.
[Test cases]
1) Configure netplan for static addresses for IPv6, dns settings, but no IPv4 configuration:
[...]
ens8:
accept-ra: false
addresses: ['23:b0:
nameservers:
addresses: ['f2:9d:
search: [lab, home]
renderer: NetworkManager
2) Verify that no IPv4 configuration was added in NetworkManager:
'nmcli'
3) Verify that warnings aren't in /var/log/syslog about invalid properties.
[Regression potential]
Possible regressions might include issues with setting DNS search domains or addresses for the nameservers. Any issues related to resolving addresses on such an IPv6 network, where the nameserver or search domains are incorrectly added.
---
In an IPv6 static setup with NetworkManager, such as the following:
ens8:
accept-ra: false
addresses: ['23:b0:
nameservers:
addresses: ['f2:9d:
search: [lab, home]
renderer: NetworkManager
we see the following error in syslog:
NetworkManager[
plan-ens8: invalid connection: ipv4.dns-search: this property is not allowed for 'method=link-local'
netplan renders an ipv4 dns search property, even though there is no configured ipv4 address. NetworkManager doesn't like this and it prevents the connection from being configured.
Changed in netplan: | |
status: | New → Fix Committed |
Changed in netplan.io (Ubuntu): | |
status: | New → Fix Released |
Changed in netplan: | |
status: | Fix Committed → Fix Released |
Changed in netplan.io (Ubuntu Bionic): | |
status: | Fix Released → Fix Committed |
netplan.io 0.40 in cosmic contains this fix.