Launchpad itself

Launchpad issue watching bugs from the Linux Kernel Bug Tracker

Bug #1774838 reported by David Ward
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Colin Watson

Bug Description

Launchpad is unable to import the status of any of the nearly 3000 bugs it is watching from the Linux Kernel Bug Tracker (https://bugs.launchpad.net/bugs/bugtrackers/linux-kernel-bugs).

For example, see this particular bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244
Notice the yellow triangle in the "Assigned to" column, and hover over it with the mouse.

Related branches

lp:~cjwatson/launchpad/bugzilla-time-fields
William Grant: Approve (code)
Diff: 108 lines (+43/-17)
3 files modified
lib/lp/bugs/doc/externalbugtracker-bugzilla-api.txt (+8/-0)
lib/lp/bugs/externalbugtracker/bugzilla.py (+13/-6)
lib/lp/bugs/tests/externalbugtracker.py (+22/-11)
lp:~cjwatson/launchpad/bugzilla-comment-creator-field
William Grant: Approve (code)
Diff: 217 lines (+50/-19)
6 files modified
lib/lp/bugs/doc/externalbugtracker-bugzilla-api.txt (+12/-5)
lib/lp/bugs/doc/externalbugtracker-bugzilla-lp-plugin.txt (+4/-4)
lib/lp/bugs/externalbugtracker/bugzilla.py (+6/-1)
lib/lp/bugs/tests/bugzilla-api-xmlrpc-transport.txt (+15/-5)
lib/lp/bugs/tests/bugzilla-xmlrpc-transport.txt (+3/-3)
lib/lp/bugs/tests/externalbugtracker.py (+10/-1)
Revision history for this message
Colin Watson (cjwatson) wrote :

OOPS-cc897b9671c3d665a9e71a8794e1ea05 is a sample OOPS from this. It's due to https://github.com/bugzilla/bugzilla/commit/7209095dbd23b037824b0c7a8c71f3249c0680cd (https://bugzilla.mozilla.org/show_bug.cgi?id=1103029). It looks like versions of Bugzilla that don't have web_time_utc guarantee that web_time is in UTC, so we can just assume a zero offset from UTC in that case.

Changed in launchpad:
importance: Undecided → Critical
status: New → Triaged
tags: added: bugwatch lp-bugs oops
Colin Watson (cjwatson)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r18679 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18679>.

tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Colin Watson (cjwatson) wrote :

This is fine as far as it goes, but testing on dogfood revealed another problem, so I've pushed another fix for review.

tags: added: qa-ok
removed: qa-needstesting
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r18684 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/18684>.

tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson)
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Colin Watson (cjwatson) wrote :

It'll take a while for all the bug watches to catch up, but this is flowing again now. For example, see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072

Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
Sean Davis (bluesabre) wrote :

Awesome, thanks Colin!

Revision history for this message
David Ward (dpward) wrote :

This fixed some of the bug watches, but many of them are still not working. For example see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771467

Is this because an additional fix is needed in the Launchpad code? Or is this because of something different (e.g. infrastructure related)?

Revision history for this message
Colin Watson (cjwatson) wrote :

The last log entry I can find related to that bug shows a failure with OOPS-0bd919facf32dce985bf3dd2eea748ca, which starts as follows:

  DisconnectionError: terminating connection due to administrator command
CONTEXT: SQL statement "UPDATE BugTaskFlat SET
                datecreated = NEW.datecreated,
                product = NEW.product,
                productseries = NEW.productseries,
                distribution = NEW.distribution,
                distroseries = NEW.distroseries,
                sourcepackagename = NEW.sourcepackagename,
                status = NEW.status,
                importance = NEW.importance,
                assignee = NEW.assignee,
                milestone = NEW.milestone,
                owner = NEW.owner,
                date_closed = NEW.date_closed
                WHERE bugtask = NEW.id"
PL/pgSQL function bugtask_maintain_bugtaskflat_trig() line 29 at SQL statement
ERROR: server conn crashed?
server closed the connection unexpectedly
 This probably means the server terminated abnormally
 before or while processing the request.

I think this is just a failure due to happening to run into a separate infrastructure bug that pops up from time to time but typically only lasts for about ten minutes, which suggests that it should work eventually. I'd leave it a few more days to see if it catches up, but otherwise file a new bug.

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.