whoopsie reuses CRASH_DB_IDENTIFIER on next run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie (Ubuntu) |
Fix Released
|
Low
|
Brian Murray |
Bug Description
On Vivid, Ubuntu 15.04, I observed the following behavior.
bdmurray@
[sudo] password for bdmurray:
whoopsie stop/waiting
bdmurray@
[11:07:17] Using lock path: /var/crash/
[11:07:18] The default IPv4 route is: /org/freedeskto
[11:07:18] Not a paid data plan: /org/freedeskto
[11:07:18] Found usable connection: /org/freedeskto
[11:07:18] online
bdmurray@
deadbeefbd89cc5
bdmurray@
whoopsie start/running, process 9083
bdmurray@
deadbeefbd89cc5
Notice, how the same CRASH_DB_IDENTIFIER was used by whoopsie when starting up, rather than calculating the system identifier. This may lead to crashes being reported under the wrong system-identifier if people switch from setting the environmental variable to just running whoopsie.
Changed in whoopsie (Ubuntu): | |
importance: | Undecided → Low |
Changed in whoopsie (Ubuntu): | |
status: | New → Confirmed |
tags: | added: rls-w-incoming |
Changed in whoopsie (Ubuntu): | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | Confirmed → In Progress |
This will mean that tests in CI will negligibly skew the results, but I think we can live with that for now. I agree that this is low priority.