Bugzilla.getExternalBugTrackerToUse() doesn't handle some non LP-Plugin Bugzillas correctly

Bug #246285 reported by Graham Binns
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Graham Binns

Bug Description

We're seeing a lot of errors from Bugzilla.getExternalBugTrackerToUse(), raised when attempting to call Launchpad.plugin_version() on the remote server. This is because we currently re-raise all ProtocolErrors that occur in getExternalBugTrackerToUse() whose error code isn't 404. Unfortunately, different Bugzillas seem to handle the calling of non-existent methods differently. Some (version 3.2, as far as I can tell) raise an XML-RPC Fault, others return an HTTP 500 error.

We already handle any raised Faults correctly; we should handle the HTTP 500s correctly, too.

Graham Binns (gmb)
Changed in malone:
assignee: nobody → gmb
importance: Undecided → High
milestone: none → 1.99
status: New → In Progress
Revision history for this message
Graham Binns (gmb) wrote :

Landed in r6657.

Changed in malone:
status: In Progress → Fix Committed
Graham Binns (gmb)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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