[Bug 1629797] Re: cloud-init seems to take most of yakkety slow boot time
Dan Watkins
daniel.watkins at canonical.com
Mon Oct 3 11:53:34 UTC 2016
In yakkety, a "resolve" service has been added to the hosts line in
nsswitch.conf[0]. Removing this service fixes the boot time issue.
[0] http://paste.ubuntu.com/23269859/ is the diff of nsswitch.conf between xenial and yakkety.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
** Summary changed:
- cloud-init seems to take most of yakkety slow boot time
+ resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before systemd-resolved is up
Status in cloud-init package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
New
Bug description:
Seems yakkety is consistently taking 2-3 minutes to boot on EC2 and
GCE, compared to the ~30 seconds of the first boot and ~10 seconds
thereafter in xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions
More information about the foundations-bugs
mailing list