Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3065
** Bug watch added: github.com/canonical/cloud-init/issues #3065
https://github.com/canonical/cloud-init/issues/3065
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
This bug was fixed in the package systemd - 234-2ubuntu12.3
---
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix k
See my attached log for verification of artful.
--
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
** Attachment added: "verification log on artful"
https://bugs.launchpad.net/cloud-init/+bug/1734167/+attachment/5081507/+files/lp-1734167-verify-artful.txt
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You receiv
Hello Michael, or anyone else affected,
Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Description changed:
+ [Impact]
+
+ * resolved does not start early enough in the boot-process preventing
+ DNS resolution to be operational during early boot, for example as
+ required by special early stages of cloud-init, resulting in failure to
+ boot / provision the instance fully.
+
+
** Tags added: id-5a1c7e7be1c6883c5a843d1f
--
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 clou
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/";
qemu-system-x86_64 -enable-kvm -m 768 \
-net
This bug was fixed in the package systemd - 235-3ubuntu3
---
systemd (235-3ubuntu3) bionic; urgency=medium
* netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
* resolved.service: set DefaultDependencies=no (LP: #1734167)
* systemd.postinst: enable persistent jou
Dimitri,
What is the fix that you put in? I assume it was to systemd ?
--
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 laun
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => In Progress
--
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 a
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
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
** Description changed:
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.githubuserconte
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
We will still need something that helps ensure systemd-resolved runs we
reach network-online.target; and I suspect (though I've not validated
yet) that we really want systemd-resolved to be running prior to
systemd-networkd such that systemd-networkd can relay DNS configuration
info retrieved from
I agree that systemd-resolved should be DefaultDependencies=no.
Of the individual dependencies of sysinit.target.wants, I'm guessing it
should be After=systemd-journald.service systemd-machine-id-
commit.service and possibly After=systemd-random-seed.service.
--
You received this bug notificatio
I suspect because in bionic/artful we're missing resolvconf package, that the
systemd-resolved service ends up starting later in boot. The
systemd-resolved-update-resolveconf.{service,path} require /sbin/resolvconf to
run; this service had a path-based trigger that would get hooked whenever DH
To be clear, the suggestion that xnox made causes a ordering cycle.
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
zesty does not show this problem. neither does xenial. I reflected that
in the status.
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Artful)
Importance: M
zesty does not show this problem. neither does xenial. I reflected that
in the status.
$ sudo journalctl -b -o short-monotonic | pastebinit
http://paste.ubuntu.com/26035779/
$ sudo journalctl -o short-precise | pastebinit
http://paste.ubuntu.com/26035774/
Nov 24 17:49:25.193028 ubuntu systemd[1]:
that ordering cycle is if we add 'After=systemd-resolved.service' to
cloud-init.service.
--
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
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
smoser, i think changing it in systemd unit might be better.
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecide
I think the primary issue is that cloud-init.service is depending on using the
network fully.
cloud-init.service runs:
After=networking.service
After=systemd-networkd-wait-online.service
Before=network-online.target
But systemd-resolved.service runs
After=systemd-networkd.service network.t
Heres some more info that is from failed system using bionic.
$ sudo journalctl -o short-monotonic --no-pager | pastebinit
http://paste.ubuntu.com/26035621/
$ sudo base64
/run/log/journal/7ba07d79c32c4103aefee168e433d847/system@e9ae467d022046f0a034147c78254ae9-0001-00055ebdb4f0260b.jo
$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server-
cloudimg-amd64.img
## set up dns locally for 'qemu-host' to the default ip for user networking.
$ grep qemu-host /etc/hosts
10.0.2.2 qemu-host
$ cat data/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh
26 matches
Mail list logo
