Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2737
** Bug watch added: github.com/canonical/cloud-init/issues #2737
https://github.com/canonical/cloud-init/issues/2737
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Given https://bugs.freedesktop.org/show_bug.cgi?id=98254 and
https://github.com/systemd/systemd/pull/7609 and
https://bugs.launchpad.net/ubuntu/artful/+source/systemd/+bug/1734167
this is not solved, is it?
we cannot pull dbus earlier, and pulling resolved earlier means it will
not reconnect to
** Changed in: dbus (Ubuntu)
Milestone: ubuntu-16.11 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf adds 25
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
This is fixed in cloud-init 0.7.9.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before
Marking this verified.
I booted an instance in gce.
## launch an instance
project="smoser-00"
# from gcloud compute images list ubuntu-1604-xenial-v20161115
img="/ubuntu-os-cloud/ubuntu-1604-xenial-v20161115"
name="smfoo3"
zone="us-east1-b"
mtype="f1-micro"
gcloud compute
** Merge proposal linked:
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/311163
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310547
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
** Also affects: dbus (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: dbus (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
Discussed that upstream: The gist of it is:
- 8< --
if you want to be an early boot service, then you should use something like
this:
Before=sysinit.target
And that's all.
Inserting yourself between the sockets and the regular services (which your
suggested deps do)
** Bug watch added: freedesktop.org Bugzilla #98254
https://bugs.freedesktop.org/show_bug.cgi?id=98254
** Also affects: dbus via
https://bugs.freedesktop.org/show_bug.cgi?id=98254
Importance: Unknown
Status: Unknown
** Changed in: dbus (Ubuntu)
Status: Triaged => In
This bug was fixed in the package cloud-init - 0.7.8-15-g6e45ffb-
0ubuntu1
---
cloud-init (0.7.8-15-g6e45ffb-0ubuntu1) yakkety; urgency=medium
* New upstream snapshot.
- systemd: Run cloud-init.service Before dbus.socket not dbus.target
[Daniel Watkins] (LP: #1629797).
To determine if this has been fixed, boot an image that has the GCE data
source enabled (e.g. the image from cloud-images.ubuntu.com) but not on
GCE. Examine the output of `journalctl` and look for the following
lines:
Oct 07 16:17:39 ubuntu cloud-init[1009]: [CLOUDINIT] __init__.py[DEBUG]:
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf
** Merge proposal linked:
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/307927
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This bug was fixed in the package cloud-init - 0.7.8-14-g94fd35e-
0ubuntu1
---
cloud-init (0.7.8-14-g94fd35e-0ubuntu1) yakkety; urgency=medium
* New upstream snapshot.
- systemd: run cloud-init.service Before dbus.service (LP: #1629797)
- unittests: fix use of mock 2.0
Early in z-series we should look into starting D-Bus ealier, to fix this
in a more generic fashion.
** Package changed: systemd (Ubuntu) => dbus (Ubuntu)
** Changed in: dbus (Ubuntu)
Milestone: None => ubuntu-16.11
** Changed in: dbus (Ubuntu)
Assignee: (unassigned) => Martin Pitt
Intent is to work around this in cloud-init via 'Before=dbus.socket'.
** Changed in: cloud-init (Ubuntu)
Status: Invalid => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu)
Assignee: Dan Watkins
So, the root cause is completely clear: dbus.socket starts early, then
cloud-init starts which blocks the entire basic.target (early boot) on
network operations, thus dbus.service cannot start. nss-resolve already
sees dbus.socket and thus can connect (instead of failing fast), and
then gets the
Simpler reproducer without cloud-init: Add "ExecStartPre=/bin/sleep
1000" to /lib/systemd/system/dbus.service. This happens if dbus.socket
is already running, but dbus.service isn't yet as it's blocked by cloud-
init.service.
--
You received this bug notification because you are a member of
A convenient way to test this is to install libnss-resolve and cloud-
init into a yakkety container. Then cloud-init will basically hang
forever, looping on
2016-10-04 12:58:48,716 - url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[100/120s]:
Adding After=systemd-resolved.service to /lib/systemd/system/cloud-
init.service causes the following in journalctl:
Oct 03 12:05:04 yakkety-161003-0945 systemd[1]: basic.target: Found ordering
cycle on basic.target/start
Oct 03 12:05:04 yakkety-161003-0945 systemd[1]: basic.target: Found
23 matches
Mail list logo
