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
I've tested this on precise, trusty, and xenial and confirm that it
works as designed. Thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Hello Scott, 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
h
This bug was fixed in the package pollinate - 4.18-0ubuntu2~16.04
---
pollinate (4.18-0ubuntu2~16.04) xenial-proposed; urgency=medium
* debian/pollinate.service: Move installation from network.target to
multi-user.target. network.target is too early and causes dependency loops
Releasing this early as this is a regression in 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/1576333
Title:
runs to early, causes dependency loops
To manage notifications about thi
** 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/1576333
Title:
runs to early, causes dependency loops
To manage notifications about this bug go to:
https://bugs.launchp
http://autopkgtest.ubuntu.com/packages/n/nfs-utils/yakkety/amd64/ passes
again (same fix in yakkety).
I ran the test case in a VM with the xenial-proposed package and confirm
that both network-online.target and pollinate.service run correctly, and
there are no dependency loops any more.
** Tags r
Hello Scott, 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-0ubuntu2~16.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
This bug was fixed in the package pollinate - 4.18-0ubuntu2
---
pollinate (4.18-0ubuntu2) yakkety; urgency=medium
* debian/pollinate.service: Move installation from network.target to
multi-user.target. network.target is too early and causes dependency loops
with e. g. NFS. (
** Description changed:
The first half of the original bug report got fixed in bug 1578833, but
pollinate still runs to early.
SRU INFORMATION
===
Impact: Causes service failures during boot when using NFS mounts, regression
from bug 1578833
Reproducer:
- - sudo apt-ge
** Description changed:
+ The first half of the original bug report got fixed in bug 1578833, but
+ pollinate still runs to early.
+
+ SRU INFORMATION
+ ===
+ Impact: Causes service failures during boot when using NFS mounts, regression
from bug 1578833
+ Reproducer:
+ - sudo apt-ge
This was actually attempted to get fixed in
https://launchpad.net/ubuntu/+source/pollinate/4.18-0ubuntu1, see commit
http://bazaar.launchpad.net/~pollinate/pollinate/trunk/revision/306 .
However, when we did this we were missing the "WantedBy=network.target"
which will still attempt to start it ea
Bumping to critical as this is a regression in the recent Xenial SRU.
** Summary changed:
- runs to early
+ runs to early, causes dependency loops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157633
> +After=network.target
network.target is mostly just relevant for a correct shutdown order,
thus it's irrelevant. You want "After=network-online.target" instead
(see man systemd.special). But if you do this, you have to give up on
running this during early boot (DefaultDependencies=no) as the
net
14 matches
Mail list logo