Freedesktop bug watches are (incorrectly) updated with "importance unknown"

Bug #707478 reported by Marcel Stimberg
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Gavin Panella

Bug Description

For a lot of old, untouched bugs the upstream status of freedesktop bugzilla bugwatches is updated to "Importance: unknown" even though the upstream bug has not been updated at all and the importance is still set to Medium/High/etc.
One example is the following bug:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/397617
Another one:
https://bugs.launchpad.net/ubuntu/+source/sun-java5/+bug/86103

This generates a lot of confusing email noise...

Tags: bugwatch qa-ok

Related branches

description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

I'm seeing it too all of a sudden this morning, across hundreds of bug reports.

Unless something changed in the bugtracker code, I'm wondering if freedesktop changed their bugzilla or something?

Changed in launchpad:
status: New → Confirmed
Revision history for this message
Deryck Hodge (deryck) wrote :

Bryce and I chatted on IRC about this and he did some digging to see what might be going on, but we don't have much more info to share. This seems to only affect the Freedesktop.org bug tracker, which would indicate something changing on their end. I'm hopeful someone on one of the maintenance squads can take a look soon, since bug watches won't be correctly updated due to this.

Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → High
tags: added: bugwatch
Revision history for this message
Deryck Hodge (deryck) wrote :

to be extra clear -- bug watches against Freedesktop Bugzilla won't be correctly updated due to this.

Revision history for this message
Bryce Harrington (bryce) wrote :

One change I found (which affected one of my own scripts) is that their new bug form no longer works when sent data via POST. Changing my script to use GET instead seems to have fixed it. That script had stopped working about a month or so ago. It makes me wonder, if the LP bz importer thingee runs only once a month, and uses POST to collect importance values, if it might have been affected but took until now to notice it?

Revision history for this message
Bryce Harrington (bryce) wrote :

Btw, I went through the HTML of the new bug form in detail to see if any fields have changed, but none had. So I think this is probably not an issue with the fdo bugzilla bug format changing.

Also, I reviewed the changelog they have posted here: https://bugs.freedesktop.org/page.cgi?id=release-notes.html This indicates they're running version 3.4.6, which they announced upgrading to last April (http://www.freedesktop.org/admin/blog/2010/Apr/02) so I don't think it is a software/application change.

Wild guess would be that they restricted POST in some fashion while doing some security update or other. However I'm not seeing mention of it anywhere. http://www.freedesktop.org/admin/blog/ has no entries since April. http://www.fooishbar.org/blog/tech/fdo/gabe-2007-05-08-17-27.html mentions some DNS troubles they dealt with recently, but indicates bugzilla was not affected.

Anyway, hope this gives y'all something to go on.

Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Raising to Critical as this is an operational issue.

Changed in launchpad:
importance: High → Critical
Revision history for this message
Brian Murray (brian-murray) wrote :

Perhaps the bug watch updater shouldn't change importances from a known value to Unknown.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 707478] Re: Freedesktop bug watches are (incorrectly) updated with "importance unknown"

On Wed, Jan 26, 2011 at 8:38 AM, Brian Murray <email address hidden> wrote:
> Perhaps the bug watch updater shouldn't change importances from a known
> value to Unknown.

Possibly; but if it knows it has changed, but not what too, what
should it do? Regardless, will ping sinzui and bigjools as current
maintenance leads and see who wants it.

Changed in launchpad:
assignee: nobody → Gavin Panella (allenap)
Gavin Panella (allenap)
Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Gavin Panella (allenap) wrote :

I think I have discovered the problem - bugs.freedesktop.org used to ignore but is now recognizing the columnlist parameter we pass over, and it was wrong - and I'm landing a fix. Once this goes live all the importances are going to flip back to non-Unknown values, and people are going to get spammed all over again. There's not a lot I can do about this. However, that should be it until Launchpad and Bugzilla, or any other bug tracker we connect to, become bug-incompatible again.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.02
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Gavin Panella (allenap)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for the fix Gavin!

I for one don't mind the uberspammage since it means my importances are back where they should be. :-)

Revision history for this message
Gavin Panella (allenap) wrote :

Bryce, that's great :) We're up to 1 happy customer. I'm not counting unhappy ones ;)

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

Other bug subscribers

Remote bug watches

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