[Bug 1786726] Re: dns-search rendered for ipv4 when no addresses configured
Steve Langasek
steve.langasek at canonical.com
Thu Nov 8 17:04:54 UTC 2018
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1786726
Title:
dns-search rendered for ipv4 when no addresses configured
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
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:87:58:65:f7:fb:8b/45', '63:94:73:e1:46:15:79:58/50']
nameservers:
addresses: ['f2:9d:bc:04:7b:87:ec:28']
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:87:58:65:f7:fb:8b/45', '63:94:73:e1:46:15:79:58/50']
nameservers:
addresses: ['f2:9d:bc:04:7b:87:ec:28']
search: [lab, home]
renderer: NetworkManager
we see the following error in syslog:
NetworkManager[19666]: <warn> [1532665946.1502] keyfile: error loading connection from file /run/NetworkManager/system-connections/net
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1786726/+subscriptions
More information about the foundations-bugs
mailing list