Trying to upgrade from Xenial to Bionic we think we've hit this bug.
Previously in xenial we used resolvconf from bootcmd to override the DNS
server. This no longer works in Bionic.
We switched to using the "network" section in cloud init as below:
network:
version: 1
config:
- type: physical
name: eth0
subnets:
- type: dhcp
dns_nameservers:
- 172.29.248.2
This config has an effect in xenial but is broken - we get
"__init__.py[DEBUG]: no interfaces to rename". No idea why renaming has
anything to do with anything, as we're just trying to set a nameserver
on an existing interface.
This config in turn has no effect at all in bionic - the DNS server
172.29.248.2 doesn't appear in any logfile.
It seems it's impossible to use bionic as a nameserver, given you cannot
override the DHCP provided nameserver to point upstream, and you cannot
configure the nameserver because the nameserver is required to download
the packages to implement the nameserver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Title:
Fail to set DNS server and search domain when customize Ubuntu18.04 to
DHCP IP by cloud-init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
