group.of.nepali.translators team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

** Also affects: pollinate (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: pollinate (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: pollinate (Ubuntu Xenial)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: pollinate (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1578833

Title:
  pollinate should not run in containers and only for first boot

Status in pollinate package in Ubuntu:
  Fix Released
Status in pollinate source package in Xenial:
  Triaged

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1578833/+subscriptions