whoopsie should record OOPS ID for an uploaded crash

Bug #1326000 reported by Brian Murray on 2014-06-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Daisy
High
Brian Murray
whoopsie (Ubuntu)
High
Brian Murray
Trusty
Medium
Brian Murray

Bug Description

[Impact]
It is hard for a developer to determine the OOPS at errors.ubuntu.com associated with the crash file that they uploaded, especially if they have uploaded multiple .crash files. This resolves this by having daisy return the OOPS ID when the report is uploaded, which is then logged by whoopsie.

[Test Case]
1) start whoopsie in the foreground "sudo CRASH_DB_URL=https://daisy.ubuntu.com APPORT_REPORT_DIR=/var/crash/ whoopsie -f"
2) start d-feet in a terminal "d-feet &"
3) pkill -11 d-feet
4) say yes to reporting the crash
5) Observe the following in the terminal running whoopsie
Parsing /var/crash/_usr_share_virt-manager_virt-manager.py.1000.crash.
Uploading /var/crash/_usr_share_virt-manager_virt-manager.py.1000.crash.
Sent; server replied with: No error
Response code: 200
Sent; server replied with: No error

With the version of whoopsie from trusty -proposed you will see the following line:

"Reported OOPS ID 89d2d5fc-f0af-11e3-8891-fa163e373683"

You can then go to https://errors.ubuntu.com/oops/$OOPSID and see the crash you reported (it should be about the same package).

[Regression Potential]
There is little chance of a regression as we are just logging more information.

When whoopsie uploads a crash to errors.ubuntu.com the OOPS ID for the crash should be recorded by whoopsie in a log file. This would require some work on daisy's part to return the OOPS ID. This would allow one to more easily find the OOPS corresponding to a crash then going to the user page and looking at all of the most recent OOPSes to find the one you are interested in.

Brian Murray (brian-murray) wrote :

This may be a good target for SRU'ing to Trusty.

Changed in whoopsie (Ubuntu):
importance: Undecided → High
Changed in daisy:
status: New → Fix Committed
importance: Undecided → Medium
importance: Medium → High
assignee: nobody → Brian Murray (brian-murray)
Changed in whoopsie (Ubuntu):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
Brian Murray (brian-murray) wrote :

The whoopsie fix is dependent upon r447 of daisy being deployed.

Brian Murray (brian-murray) wrote :

r447 of daisy has been deployed.

Changed in whoopsie (Ubuntu Trusty):
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie - 0.2.31

---------------
whoopsie (0.2.31) utopic; urgency=medium

  * Log the OOPS ID (returned by daisy) for the reported crash. (LP: #1326000)
 -- Brian Murray <email address hidden> Mon, 09 Jun 2014 10:49:55 -0700

Changed in whoopsie (Ubuntu):
status: In Progress → Fix Released
description: updated
Brian Murray (brian-murray) wrote :

I've uploaded the fix for this to the -proposed queue for Trusty.

Hello Brian, or anyone else affected,

Accepted whoopsie into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/whoopsie/0.2.24.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in whoopsie (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in daisy:
status: Fix Committed → Fix Released
Brian Murray (brian-murray) wrote :

With the version of whoopsie from trusty-proposed I saw the following in my syslog file (grep whoopsie /var/log/syslog).

Jun 11 22:46:07 blacklightning whoopsie[18099]: online
Jun 11 22:46:07 blacklightning whoopsie[18099]: Parsing /var/crash/_usr_bin_d-feet.1000.crash.
Jun 11 22:46:07 blacklightning whoopsie[18099]: Uploading /var/crash/_usr_bin_d-feet.1000.crash.
Jun 11 22:46:43 blacklightning whoopsie[18099]: Sent; server replied with: No error
Jun 11 22:46:43 blacklightning whoopsie[18099]: Response code: 200
Jun 11 22:46:43 blacklightning whoopsie[18099]: Reported OOPS ID 70534ee0-f1a9-11e3-8b50-fa163e373683

And going to https://errors.ubuntu.com/oops/70534ee0-f1a9-11e3-8b50-fa163e373683 we can see it is a crash about d-feet from June 11th.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie - 0.2.24.6

---------------
whoopsie (0.2.24.6) trusty-proposed; urgency=medium

  * Log the OOPS ID (returned by daisy) for the reported crash. (LP: #1326000)
 -- Brian Murray <email address hidden> Mon, 09 Jun 2014 11:03:32 -0700

Changed in whoopsie (Ubuntu Trusty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for whoopsie has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers