oopsrepository

"First seen" version is wrong in release-specific table

Bug #1056061 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Errors
Invalid
High
Unassigned
oopsrepository
Fix Released
Undecided
Unassigned

Bug Description

On the errors.ubuntu for the "crash" in ubiquity launchpad bug 1027648 the following first/last found version numbers are reported, depending on which distro series are selected:

all: ubiquity 2.10.8 2.12.2
12.04: ubiquity 2.10.20 2.10.20
12.10: ubiquity 2.12.2 2.12.2

The "all distro series" version numbers look ok, the per-series simply show the current/highest version number of the package in that distro-series in both columns, which is not the full picute as the bug did indeed exist all the way throughout 2.108 & 2.12.2.

It may save time to fix bug 1021326 at the same time as this bug.

See original description

Related branches

lp://staging/~ev/oops-repository/whoopsie-daisy
j.c.sackett (community): Approve
Robert Collins: Pending requested
Diff: 454 lines (+94/-114)
8 files modified
oopsrepository/cassandra.py (+1/-1)
oopsrepository/oopses.py (+0/-94)
oopsrepository/schema.py (+17/-1)
oopsrepository/testing/cassandra.py (+1/-1)
oopsrepository/testing/matchers.py (+11/-2)
oopsrepository/tests/test_matchers.py (+1/-1)
oopsrepository/tests/test_oopses.py (+62/-13)
oopsrepository/tests/test_schema.py (+1/-1)
Dimitri John Ledkov (xnox)
description: updated
Matthew Paul Thomas (mpt)
Changed in errors:
status: New → Triaged
importance: Undecided → High
summary: - first/last found version are odd between all & per-distro views
+ "First seen" version is wrong in release-specific table
Matthew Paul Thomas (mpt)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

I've now seen this with gparted and the row with the bug report 1063109. If you filter for the release Ubuntu 12.10 you see the first version as being 0.12.1-1ubuntu1. However, it has also occurred with 0.12.1 which is also in Ubuntu 12.10.

Revision history for this message
Brian Murray (brian-murray) wrote :

Looking at it further the api call has the wrong first_seen:

https://errors.ubuntu.com/api/1.0/most-common-problems/?format=json&release=Ubuntu%2012.10&package=gparted&period=month

    {
      "count": 8,
      "first_seen": "0.12.1-1ubuntu1",
      "function": "/usr/sbin/gpartedbin:6:ped_assert:ped_device_read:ped_geometry_read:GParted::GParted_Core::get_filesystem:GParted::GParted_Core::set_device_partitions",
      "last_seen": "0.12.1-1ubuntu1",
      "package": "gparted",
      "rank": 3,
      "report": ""
    },

Revision history for this message
Brian Murray (brian-murray) wrote :

Digging into it further it appears that something may be incorrectly writing to the database:

In [6]: cassandra.get_metadata_for_bucket('/usr/sbin/gpartedbin:6:ped_assert:ped_device_read:ped_geometry_read:GParted::GParted_Core::get_filesystem:GParted::GParted_Core::set_device_partitions')
Out[6]: OrderedDict([(u'FirstSeen', '0.11.0-2'), (u'LastSeen', '0.12.1-1ubuntu1'), (u'Source', 'gparted')])

In [7]: cassandra.get_metadata_for_bucket('/usr/sbin/gpartedbin:6:ped_assert:ped_device_read:ped_geometry_read:GParted::GParted_Core::get_filesystem:GParted::GParted_Core::set_device_partitions', 'Ubuntu 12.10')
Out[7]: OrderedDict([(u'FirstSeen', '0.12.1-1ubuntu1'), (u'LastSeen', '0.12.1-1ubuntu1'), (u'Source', 'gparted'), (u'~Ubuntu 12.04:FirstSeen', '0.11.0-2'), (u'~Ubuntu 12.04:LastSeen', '0.11.0-2'), (u'~Ubuntu 12.10:FirstSeen', '0.12.1-1ubuntu1'), (u'~Ubuntu 12.10:LastSeen', '0.12.1-1ubuntu1')])

https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fsbin%2Fgpartedbin%3A6%3Aped_assert%3Aped_device_read%3Aped_geometry_read%3AGParted%3A%3AGParted_Core%3A%3Aget_filesystem%3AGParted%3A%3AGParted_Core%3A%3Aset_device_partitions

Clearly there are some from 12.10 using 0.12.1.

Revision history for this message
Evan (ev) wrote :

http://paste.ubuntu.com/5596388/

Brian Murray (brian-murray)
Changed in oops-repository:
status: New → Confirmed
Revision history for this message
Evan (ev) wrote :

Fixed in r61.

Changed in oops-repository:
status: Confirmed → Fix Committed
Evan (ev)
Changed in oops-repository:
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

This has been fixed in oopsrepository and as more errors are being bucketed the data will eventually be correct. I'm going to close the Errors task as Invalid as I don't think it is necessary to run a special job to clean this up.

Changed in errors:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.