Public bug reported:
Booting a xenial cloud image in lxd shows that pollinate by far is the
biggest bottleneck:
$ systemd-analyze blame
2.756s pollinate.service
656ms cloud-init-local.service
598ms cloud-init.service
509ms cloud-config.service
393ms cloud-final.service
147ms networking.service
[...]
This is the second boot, so cloud-init should not actually do anything
any more (it takes muuuch longer on the first boot).
pollinate should not run in containers at all, as containers take
randomness from the host. Also, for VMs it should only run for the first
boot. Both upstart and systemd save the random seed on shutdown and load
it at boot, which is a lot faster than pollinate.
So pollinate.service should grow
ConditionVirtualization=!container
ConditionPathExists=!/var/lib/systemd/random-seed
** Affects: pollinate (Ubuntu)
Importance: Undecided
Status: New
** Tags: bootspeed cloud-image xenial
** Tags added: bootspeed
** Tags added: cloud-image xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578833
Title:
pollinate should not run in containers and only for first boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1578833/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
