| 2017-07-24 20:34:36 |
Brian Murray |
bug |
|
|
added bug |
| 2017-07-24 20:34:51 |
Brian Murray |
tags |
|
artful |
|
| 2017-07-24 20:34:56 |
Brian Murray |
whoopsie (Ubuntu): status |
New |
Triaged |
|
| 2017-07-24 20:34:59 |
Brian Murray |
whoopsie (Ubuntu): importance |
Undecided |
High |
|
| 2017-07-24 20:49:02 |
Brian Murray |
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 it:
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 |
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 |
|
| 2017-07-25 18:42:36 |
Brian Murray |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-07-25 18:42:36 |
Brian Murray |
bug task added |
|
whoopsie (Ubuntu Zesty) |
|
| 2017-07-25 18:42:36 |
Brian Murray |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-07-25 18:42:36 |
Brian Murray |
bug task added |
|
whoopsie (Ubuntu Xenial) |
|
| 2017-07-25 18:42:55 |
Brian Murray |
whoopsie (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-07-25 18:42:55 |
Brian Murray |
whoopsie (Ubuntu Xenial): status |
New |
Triaged |
|
| 2017-07-25 18:42:55 |
Brian Murray |
whoopsie (Ubuntu Xenial): assignee |
|
Brian Murray (brian-murray) |
|
| 2017-07-25 18:43:03 |
Brian Murray |
whoopsie (Ubuntu Zesty): status |
New |
Triaged |
|
| 2017-07-25 18:43:06 |
Brian Murray |
whoopsie (Ubuntu Zesty): importance |
Undecided |
High |
|
| 2017-07-25 18:43:14 |
Brian Murray |
tags |
artful |
artful xenial |
|
| 2017-07-25 18:43:24 |
Brian Murray |
tags |
artful xenial |
artful xenial zesty |
|
| 2017-07-25 19:30:41 |
Brian Murray |
whoopsie (Ubuntu): assignee |
|
Brian Murray (brian-murray) |
|
| 2017-07-25 19:30:43 |
Brian Murray |
whoopsie (Ubuntu Zesty): assignee |
|
Brian Murray (brian-murray) |
|
| 2017-07-25 20:26:27 |
Brian Murray |
whoopsie (Ubuntu): status |
Triaged |
In Progress |
|
| 2017-07-25 20:26:30 |
Brian Murray |
whoopsie (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2017-07-25 20:26:33 |
Brian Murray |
whoopsie (Ubuntu Zesty): status |
Triaged |
In Progress |
|
| 2017-07-25 20:32:46 |
Brian Murray |
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 |
[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 |
|
| 2017-07-25 21:07:26 |
Brian Murray |
whoopsie (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-07-28 00:34:16 |
Adam Conrad |
whoopsie (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-07-28 00:34:18 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-07-28 00:34:19 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2017-07-28 00:34:22 |
Adam Conrad |
tags |
artful xenial zesty |
artful verification-needed verification-needed-xenial xenial zesty |
|
| 2017-07-28 00:35:02 |
Adam Conrad |
whoopsie (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
| 2017-07-28 00:35:11 |
Adam Conrad |
tags |
artful verification-needed verification-needed-xenial xenial zesty |
artful verification-needed verification-needed-xenial verification-needed-zesty xenial zesty |
|
| 2017-07-28 08:49:05 |
paz |
bug |
|
|
added subscriber paz |
| 2017-07-28 17:28:20 |
Brian Murray |
tags |
artful verification-needed verification-needed-xenial verification-needed-zesty xenial zesty |
artful verification-done-xenial verification-done-zesty verification-needed xenial zesty |
|
| 2017-07-31 15:01:53 |
Launchpad Janitor |
whoopsie (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-07-31 15:01:57 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-07-31 15:02:03 |
Launchpad Janitor |
whoopsie (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-09-29 17:44:11 |
Francis Ginther |
tags |
artful verification-done-xenial verification-done-zesty verification-needed xenial zesty |
artful id-59761bfbcfbdd79f928c8806 verification-done-xenial verification-done-zesty verification-needed xenial zesty |
|
