I've verified that this is reproducible within lxc, and then filed a bug i saw (bug 1734939) as a result.
Heres a trivial reproduce: ## just showing content of the url. $ curl --silent https://hastebin.com/raw/coladicuva #!/bin/sh cat /proc/uptime | tee /run/user-script-uptime $ name=btest $ lxc launch ubuntu-daily:bionic $name \ "--config=user.user-data=#include https://hastebin.com/raw/coladicuva"; $ sleep 20 $ lxc exec b4 grep WARN /var/log/cloud-init.log 2017-11-28 16:49:12,251 - user_data.py[WARNING]: HTTPSConnectionPool(host='hastebin.com', port=443): Max retries exceeded with url: /raw/coladicuva (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f20736a4e80>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)) for url: https://hastebin.com/raw/coladicuva ** Changed in: cloud-init (Ubuntu Bionic) Importance: High => Critical ** Changed in: cloud-init (Ubuntu Artful) Importance: High => Critical ** Changed in: systemd (Ubuntu Bionic) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. 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: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
