** Changed in: whoopsie (Ubuntu)
Status: Triaged => In Progress
** Changed in: whoopsie (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: whoopsie (Ubuntu Zesty)
Status: Triaged => In Progress
** Description changed:
- whoopsie's systemd service file does not start after networking which is
- incorrect since it initially needs to query network-manager's state. A
- fix was attempted by changing the service file to include "After
- =network-online.target" but this was insufficient. The following
- messages demonstrate the failure, if whoopsie were to start after
- network-manager we would not see them:
+ [Impact]
+ whoopsie can start before network-manager and then will only work when a
networking device state changes, however since it started before n-m it should
notice the connection come on-line. This is upload is just in case there are
some corner cases out there where whoopsie isn't working and uploading the
crashes to the Error Tracker.
+
+ [Test Case]
+ 1) Boot a system with the old version of whoopsie
+ 2) Run 'systemctl status whoopsie'
+ 3) Observe:
+ Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission
daemon.
+ Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path:
/var/lock/whoopsie/lock
+ Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the
Network Manager state:
+ Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01]
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
+ Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline
+
+ With the version of whoopsie in -proposed you'll see the following:
+
+ Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission
daemon.
+ Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path:
/var/lock/whoopsie/lock
+ Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4
route is: /org/freedesktop/NetworkManager/ActiveConnection/0
+ Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data
plan: /org/freedesktop/NetworkManager/ActiveConnection/0
+ Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable
connection: /org/freedesktop/NetworkManager/ActiveConnection/0
+
+ [Regression Potential]
+ If whoopsie is working properly when it wasn't, this shouldn't be the case
because whoopsie would start working when the network connection changed, then
people might be surprised by additional network activity (uploading of crashes)
and the Error Tracker may receive more crash reports.
+
+ Original Description
+ --------------------
+ whoopsie's systemd service file does not start after networking which is
incorrect since it initially needs to query network-manager's state. A fix was
attempted by changing the service file to include "After=network-online.target"
but this was insufficient. The following messages demonstrate the failure, if
whoopsie were to start after network-manager we would not see them:
Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network
Manager state:
Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47]
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706195
Title:
whoopsie can start before network-manager during boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
