Launchpad couldn't connect to ALSA Bug Tracker.

[Brian Murray]

Bug watches of ALSA bug tracker bugs are not being updated. Bug 114053 is an example of this.

Exception type BugTrackerConnectError
Exception value http://bugtrack.alsa-project.org/alsa-bug: HTTP Error 500: Internal Server Error

[Diogo Matsubara (matsubara)]

For some reason, alsa bugtracker is returning a HTTP Error 500: Internal Server Error

Related OOPS: OOPS-968CCW1994, OOPS-969CCW1944

[Eleanor Berger (intellectronica)]

Looks like the CSV export of the mantis bug tracker at alsa is broken, and returns 500 errors. We'll have to find who's the administrator of the bug tracker and let them know.

[Eleanor Berger (intellectronica)]

Actually, that's not the whole story - we should be able to fall back from using the CSV export to screen scraping, but that doesn't work correctly, so it's worth fixing regardless of the problem on the server itself

[Eleanor Berger (intellectronica)]

After testing this on several machines as well as the staging server, it now looks like the problem is with the redirect from http to https

[Eleanor Berger (intellectronica)]

confirmed. marking this as a duplicate of an existing bug about redirects from https to https. i have also changed the bug tracker information, so it should be ok in the future.

[Eleanor Berger (intellectronica)]

Maybe this isn't a dupe after all - fixing the bugtracker URL didn't solve the problem.

[Eleanor Berger (intellectronica)]

Actually, maybe it is the problem. All the relevant oopses refer to the http address, and are from before the change, so we'll have to wait for the next run to confirm.

[era (era)]

So is this a duplicate of Bug #34102?

[Gavin Panella (allenap)]

I did some investigation. It seems that, for the ALSA tracker, the return value from Mantis.csv_data is an HTML page, containing the login form (from login_page.php).

I tried detecting if the page was HTML - see the diff at http://pastebin.ubuntu.com/364577/ - and then falling back to page scraping. However, it still returned the login page.

It seems that the auto-login code in MantisLoginHandler is no longer enough to get us access. The guest user name and password we give are fine - they work in the browser - so I suspect the problem is that Mantis wants us to POST the form.

[Abel Deuring (adeuring)]

There are two problems:

  - class MantisLoginHandler was designed to be used with ClientCookie, while r7133 replaced ClientCokkie by urllib2
  - acessing the CSV data URL on the Alsa bug tracker leads to HTTP 500 error.

[Ursula Junque (ursinha)]

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

[Ursula Junque (ursinha)]

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

[Abel Deuring (adeuring)]

The code changes pass several tests: Running cronscripts/checkwatches.py works (mostly) fine on staging for several Mantis trackers; running the method Mantis.initializeRemoteBugDB() with all Alsa related bugs work fine on a development machine (except for bug 570263).

One problem remains: Attempts to access the Alsa bug tracker from staging result in "Connection Refused" HTTP errors. Seems that Launchpad is blacklisted by the Alsa tracker. I contacted their webmaster to see what we can do to remedy this.