group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1578833@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package pollinate - 4.18-0ubuntu1~16.04

---------------
pollinate (4.18-0ubuntu1~16.04) xenial-proposed; urgency=medium

  * debian/pollinate.service:
    - move to later in boot, after network starts, but before ssh starts

pollinate (4.17-0ubuntu1) yakkety; urgency=medium

  * debian/pollinate.service:
    - use the right flag file for LP: #1578833

pollinate (4.16-0ubuntu1) yakkety; urgency=medium

  [ Martin Pitt ]
  * Don't run pollinate.service in containers (as containers can't and should
    not write the host's random pool) and when we already have a saved random
    seeds (i. e. only on first boot). (LP: #1578833)
  * Bump Standards-Version to 3.9.8 (no changes needed).

  [ Dustin Kirkland ]
  * pollinate: use timeout(1) to limit curl, related to LP: #1578833

 -- Dustin Kirkland <kirkland@xxxxxxxxxx>  Fri, 06 May 2016 11:36:02
-0500

** Changed in: pollinate (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
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:
  Fix Released

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

  == SRU ==

  [IMPACT]
  Some Xenial boots take longer than they should.  Pollinate should only run once, at first boot, and never in containers.  And should never take longer than 3 seconds.

  [TEST CASE]
  Boot a new Xenial instance.  Ensure that pollinate runs the first time it boots.  You can check that in /var/log/syslog and ensure that /var/cache/pollinate/seeded exists /var/cache/pollinate/log.  Now reboot that instance.  Ensure that more, new entries do *not* show up.

  [REGRESSION POTENTIAL]
  The regression potential is important.  We need to ensure that we don't somehow *never* pollinate the first time.

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