| 2016-10-03 08:47:46 |
Jose L. VG |
bug |
|
|
added bug |
| 2016-10-03 08:49:12 |
Jose L. VG |
attachment added |
|
TestingyakketybootspeedregressionvsxenialinEC2.odt https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+attachment/4753367/+files/TestingyakketybootspeedregressionvsxenialinEC2.odt |
|
| 2016-10-03 08:50:41 |
Dan Watkins |
cloud-init (Ubuntu): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
| 2016-10-03 09:05:12 |
Dan Watkins |
description |
Seems yakkety is consistently taking 2-3 minutes to boot on EC2, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. |
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. |
|
| 2016-10-03 11:54:11 |
Dan Watkins |
bug task added |
|
systemd (Ubuntu) |
|
| 2016-10-03 11:54:25 |
Dan Watkins |
cloud-init (Ubuntu): status |
New |
Invalid |
|
| 2016-10-03 11:55:05 |
Dan Watkins |
summary |
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 |
|
| 2016-10-03 12:05:17 |
Dan Watkins |
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. |
During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does-not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments.
This means that 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. |
|
| 2016-10-04 13:00:30 |
Martin Pitt |
systemd (Ubuntu): status |
New |
Triaged |
|
| 2016-10-04 13:36:36 |
Martin Pitt |
bug |
|
|
added subscriber Martin Pitt |
| 2016-10-04 19:33:36 |
Scott Moser |
cloud-init (Ubuntu): status |
Invalid |
In Progress |
|
| 2016-10-04 19:33:41 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Critical |
|
| 2016-10-04 19:34:28 |
Scott Moser |
cloud-init (Ubuntu): assignee |
Dan Watkins (daniel-thewatkins) |
Scott Moser (smoser) |
|
| 2016-10-04 19:36:03 |
Martin Pitt |
affects |
systemd (Ubuntu) |
dbus (Ubuntu) |
|
| 2016-10-04 19:36:03 |
Martin Pitt |
dbus (Ubuntu): milestone |
|
ubuntu-16.11 |
|
| 2016-10-04 19:36:03 |
Martin Pitt |
dbus (Ubuntu): assignee |
|
Martin Pitt (pitti) |
|
| 2016-10-05 07:01:27 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-10-05 13:01:33 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-10-05 13:01:42 |
Scott Moser |
cloud-init: status |
New |
Fix Committed |
|
| 2016-10-05 13:01:47 |
Scott Moser |
cloud-init: importance |
Undecided |
High |
|
| 2016-10-07 10:41:15 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/307927 |
|
| 2016-10-07 16:11:34 |
Scott Moser |
cloud-init (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-10-07 18:32:10 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-10-14 11:45:40 |
Martin Pitt |
bug watch added |
|
https://bugs.freedesktop.org/show_bug.cgi?id=98254 |
|
| 2016-10-14 11:45:40 |
Martin Pitt |
bug task added |
|
dbus |
|
| 2016-10-14 11:51:31 |
Martin Pitt |
dbus (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-10-17 10:49:06 |
Martin Pitt |
dbus (Ubuntu): status |
In Progress |
Won't Fix |
|
| 2016-10-17 10:49:06 |
Martin Pitt |
dbus (Ubuntu): assignee |
Martin Pitt (pitti) |
|
|
| 2016-11-07 21:11:23 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-11-07 21:11:23 |
Scott Moser |
bug task added |
|
dbus (Ubuntu Yakkety) |
|
| 2016-11-07 21:11:23 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2016-11-07 21:11:23 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-11-07 21:11:23 |
Scott Moser |
bug task added |
|
dbus (Ubuntu Xenial) |
|
| 2016-11-07 21:11:23 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2016-11-07 21:11:35 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-11-07 21:11:37 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2016-11-07 21:11:40 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-11-07 21:11:43 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-11-07 21:11:49 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Released |
|
| 2016-11-07 21:11:55 |
Scott Moser |
dbus (Ubuntu Xenial): status |
New |
Invalid |
|
| 2016-11-07 21:11:59 |
Scott Moser |
dbus (Ubuntu Yakkety): status |
New |
Invalid |
|
| 2016-11-07 21:12:07 |
Scott Moser |
bug task deleted |
dbus (Ubuntu Xenial) |
|
|
| 2016-11-07 21:12:13 |
Scott Moser |
bug task deleted |
dbus (Ubuntu Yakkety) |
|
|
| 2016-11-07 21:17:06 |
Scott Moser |
description |
During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does-not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments.
This means that 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. |
=== Begin SRU Template ===
[Impact]
In cases where cloud-init used dns during early boot and system was
configured in nsswitch.conf to use systemd-resolvd, the system would
timeout on dns attempts making system boot terribly slow.
[Test Case]
Boot a system on GCE.
check for WARN in /var/log/messages
check that time to boot is reasonable (<30 seconds). In failure case the
times would be minutes.
[Regression Potential]
Changing order in boot can be dangerous. There is real chance for
regression here, but it should be fairly small as xenial does not include
systemd-resolved usage. This was first noticed on yakkety where it did.
[Other Info]
It seems useful to SRU this in the event that systemd-resolvd is used
on 16.04 or the case where user upgrades components (admittedly small use
case).
=== End SRU Template ===
During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does-not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments.
This means that 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. |
|
| 2016-11-10 15:55:21 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310547 |
|
| 2016-11-17 15:57:25 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/311163 |
|
| 2016-11-22 04:43:09 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2016-11-22 04:43:49 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Confirmed |
|
| 2016-12-23 17:38:59 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2017-03-02 01:03:46 |
Mathew Hodson |
dbus (Ubuntu): milestone |
ubuntu-16.11 |
|
|
| 2023-05-10 17:05:22 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2737 |
|
