<xnox> smoser, yeah, so like cloud-init.service should want/after
systemd-resolved.service; or e.g. systemd-resolved.service should declare
itself before cloud-init.service
<xnox> smoser, i think changing it in systemd unit might be better.
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Also affects: systemd (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in no-cloud as launched by ubuntu
Status in cloud-init:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Status in cloud-init source package in Zesty:
New
Status in systemd source package in Zesty:
New
Status in cloud-init source package in Artful:
New
Status in systemd source package in Artful:
New
Status in cloud-init source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Confirmed
Bug description:
I use no-cloud to test the kernel in CI (I am maintainer of the bcache
subsystem), and have been running it successfully under 16.04 cloud
images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-
net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
metadata/linuxtst/"
As documented here:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Under the new 17.10 cloud images, this doesn't work: the network comes
up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
to a nonexistent file at this point of the boot and systemd-resolved
is not running. When I manually hack /etc/resolv.conf in the cloud
image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems
like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://,
https:// or ftp://";
And https is not going to work for a raw IP address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
