** 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-get install -y nfs-common pollinate
- - echo "1.2.3.4:/foo /mnt nfs defaults,nofail 0 0" | sudo tee -a /etc/fstab
- (This will start network-online.target during early boot)
- - sudo reboot
- - Confirm that "sudo journalctl -b -p warning" shows a dependency loop, and
most probably "systemctl status network-online.target" is not running.
- - Upgrade to the proposed pollinate update, reboot.
- - Confirm that there is no dependency loop any more and "systemctl status
network-online.target" is active.
- - Confirm that /etc/systemd/system/network.target.wants/pollinate.service
does not exist any more.
+ - sudo apt-get install -y nfs-common pollinate
+ - echo "1.2.3.4:/foo /mnt nfs defaults,nofail 0 0" | sudo tee -a /etc/fstab
+ (This will start network-online.target during early boot)
+ - sudo reboot
+ - Confirm that "sudo journalctl -b -p warning" shows a dependency loop, and
most probably "systemctl status network-online.target" is not running.
+ - Upgrade to the proposed pollinate update, reboot.
+ - Confirm that there is no dependency loop any more and "systemctl status
network-online.target" is active.
+ - Confirm that "systemctl status pollinate" is "enabled" (it will have
"start: condition failed", but that is intended).
+ - Confirm that /etc/systemd/system/network.target.wants/pollinate.service
does not exist any more.
Regression potential: Low. This merely changes when pollinate.service
gets activated, and network.target is too early (nothing should actually
be started by network.target, this is mostly meant for shutdown). The
main thing that can go wrong is that the upgrade still leaves the old
/etc/systemd/system/network.target.wants/pollinate.service symlink
behind (the maintainer scripts have to clean that up).
-
Original bug report:
pollinate runs too early on some of the instances i launch. Basically
nothing guarantees that it will have network access when it attempts to
run.
failure looks something like:
$ lxc launch xenial x1
$ sleep 4
$ lxc exec x1 systemctl status pollinate
● pollinate.service - Seed the pseudo random number generator on first boot
Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor
preset: enabled)
Active: inactive (dead) since Thu 2016-04-28 17:16:03 UTC; 1min 17s ago
Process: 86 ExecStart=/usr/bin/pollinate (code=exited, status=0/SUCCESS)
Main PID: 86 (code=exited, status=0/SUCCESS)
Apr 28 17:16:03 ubuntu systemd[1]: Starting Seed the pseudo random number
generator on first boot...
Apr 28 17:16:03 ubuntu pollinate[106]: client sent challenge to
[https://entropy.ubuntu.com/]
Apr 28 17:16:03 ubuntu pollinate[86]: <13>Apr 28 17:16:03 pollinate[86]:
client sent challenge to [https://entropy.ubuntu.com/]
Apr 28 17:16:03 ubuntu pollinate[149]: [432B blob data]
Apr 28 17:16:03 ubuntu pollinate[86]: Apr 28 17:16:03 ubuntu <13>Apr 28
17:16:03 pollinate[86]: WARNING: Network communication failed [0]\n % Total
% Received % Xferd Average Speed Time Time Time Current
Apr 28 17:16:03 ubuntu pollinate[86]: Dload
Upload Total Spent Left Speed
Apr 28 17:16:03 ubuntu pollinate[86]: [139B blob data]
Apr 28 17:16:03 ubuntu pollinate[86]: 17:16:03.859980 * Closing connection 0
Apr 28 17:16:03 ubuntu pollinate[86]: curl: (6) Could not resolve host:
entropy.ubuntu.com
Apr 28 17:16:03 ubuntu systemd[1]: Started Seed the pseudo random number
generator on first boot.
This seems like it might work:
# diff -u /lib/systemd/system/pollinate.service.dist
/lib/systemd/system/pollinate.service
--- /lib/systemd/system/pollinate.service.dist 2016-04-28
17:19:10.807971336 +0000
+++ /lib/systemd/system/pollinate.service 2016-04-28 17:19:17.839874541
+0000
@@ -2,6 +2,7 @@
Description=Seed the pseudo random number generator on first boot
DefaultDependencies=no
After=sysinit.target
+After=network.target
Before=ssh.service
[Service]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pollinate 4.15-0ubuntu1 [modified: usr/bin/pollinate]
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 28 16:39:17 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: pollinate
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: pollinate (Ubuntu Yakkety)
Status: In Progress => Fix Committed
** 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/1576333
Title:
runs to early, causes dependency loops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1576333/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
