whoopsie does not upload UnreportableReason field in crash reports
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
whoopsie (Ubuntu) |
Fix Released
|
High
|
Brian Murray | |||
Trusty |
Fix Released
|
High
|
Brian Murray | |||
Vivid |
Fix Released
|
High
|
Brian Murray | |||
Wily |
Fix Released
|
High
|
Brian Murray | |||
whoopsie-daisy (Ubuntu) | ||||||
Precise |
Fix Released
|
High
|
Brian Murray |
Bug Description
Test Case
---------
1) Edit a .crash file to have an UnreportableReason key and value e.g.
Unreportable
2) sudo service whoopsie stop
3) start whoopsie pointing to errors.
sudo CRASH_DB_URL=https:/
4) Put said .crash file in /var/crash/
5) Put a corresponding .upload file in /var/crash/
6) Observe whoopsie uploading the .crash file from the whoopsie log
[16:51:13] Reported OOPS ID 4ea43136-
7) go to errors.
8) verify the UnreportableReason appears there e.g.:
https:/
In src/whoopsie.c we can see the following:
/* We would only want this to see how many bugs would otherwise go
* unreported: */
"Unreportab
The comment isn't exactly true. apport uses the UnreportableReason key to include the following information:
"You have some obsolete package versions installed."
It'd be useful if this information was sent to the Error Tracker so that we can decide not to ask for a core dump from these crash reports. The "obsolete package versions" check is done by checking to see if the most recent available version of the package is installed, so if someone does not have -updates enabled then that pocket is not checked and "obsolete package versions" will not be present. This is desirable because the retracers will check to see if the package version is available from any pocket.
So if we send UnreportableReason to the Error Tracker we can stop asking for core dumps and retracing crashes that will fail to retrace.
However, the value for UnreportableReason is translated so this may not end up helping much.
Changed in whoopsie (Ubuntu): | |
importance: | Undecided → Low |
Changed in whoopsie (Ubuntu Precise): | |
status: | New → Triaged |
Changed in whoopsie (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in whoopsie (Ubuntu Vivid): | |
status: | New → Triaged |
Changed in whoopsie (Ubuntu Wily): | |
status: | New → Triaged |
Changed in whoopsie (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in whoopsie (Ubuntu Trusty): | |
importance: | Undecided → High |
Changed in whoopsie (Ubuntu Vivid): | |
importance: | Undecided → High |
Changed in whoopsie (Ubuntu Wily): | |
importance: | Undecided → High |
Changed in whoopsie (Ubuntu Wily): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in whoopsie (Ubuntu Vivid): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in whoopsie (Ubuntu Trusty): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in whoopsie (Ubuntu Precise): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
description: | updated |
no longer affects: | whoopsie-daisy (Ubuntu Wily) |
no longer affects: | whoopsie-daisy (Ubuntu Vivid) |
no longer affects: | whoopsie-daisy (Ubuntu Trusty) |
no longer affects: | whoopsie-daisy (Ubuntu) |
no longer affects: | whoopsie (Ubuntu Precise) |
An easy test case for the sending of UnreportableReason on a 14.04 system is downgrade multiarch-support to the version in the release pocket, while having -updates enabled, and then kill sleep. After the apport collection process is run you'll see the following in the report:
UnreportableReason:
You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:
multiarch-support