This bug was fixed in the package pollinate - 4.21-0ubuntu1~14.04
---
pollinate (4.21-0ubuntu1~14.04) trusty-proposed; urgency=medium
[ Dustin Kirkland ]
* pollinate:
- fix broken printing of binary data, this was breaking check_pollen
nagios scripts on the server
[ J
Hello Martin, or anyone else affected,
Accepted pollinate into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pollinate/4.21-0ubuntu1~14.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags removed: cloud-image
** Tags added: cloud-images
--
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 notifi
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=medi
I confirm that with the proposed package,
- pollinate does not start at all in a container (tested LXD)
- pollinate starts once in a VM, but not at the second boot any more.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because yo
Hello Martin, or anyone else affected,
Accepted pollinate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pollinate/4.18-0ubuntu1~16.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
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.
** Changed in: pollinate (Ubuntu Xenial)
Status: Triaged => In Progress
--
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
** Changed in: pollinate (Ubuntu Xenial)
Milestone: None => xenial-updates
--
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
** 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)
Im
This bug was fixed in the package pollinate - 4.16-0ubuntu1
---
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 rand
** Branch linked: lp:pollinate
--
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
** Changed in: pollinate (Ubuntu)
Status: New => Fix Committed
** Changed in: pollinate (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: pollinate (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
B
13 matches
Mail list logo
