Apport not working due to edge.launchpad.net failure

With the heading being "Network Problem"

This could be a silly question... but do you have the network up?

Really a silly question... confirmed here, and I have network (I'm writing this hehe).

Maybe this is related to bug #83974... Maybe not

Perhaps this is related to apport being disabled? If so, it should probably inform the user about this graphically.

mizar:[~] /usr/share/apport/apport
apport (pid 13984) Tue Feb 13 16:02:55 2007: apport is disabled for now until the kernel gets fixed

This appears to be a problem with edge.launchpad.net. When attempting to submit the blob to https://edge.launchpad.net/+storeblob, apport gets a 502 response:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 221, in <module>
    app.run_argv()
  File "/var/lib/python-support/python2.5/apport/ui.py", line 181, in run_argv
    self.run_report_bug()
  File "/var/lib/python-support/python2.5/apport/ui.py", line 175, in run_report_bug
    self.file_report()
  File "/var/lib/python-support/python2.5/apport/ui.py", line 434, in file_report
    upthread.exc_raise()
  File "/var/lib/python-support/python2.5/apport/REThread.py", line 37, in run
    self._retval = self.__target(*self.__args, **self.__kwargs)
  File "/var/lib/python-support/python2.5/apport/ui.py", line 67, in upload_launchpad_blob
    { 'FORM_SUBMIT': '1', 'field.blob': mime })
  File "/usr/lib/python2.5/urllib2.py", line 380, in open
    response = meth(req, response)
  File "/usr/lib/python2.5/urllib2.py", line 491, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.5/urllib2.py", line 418, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.5/urllib2.py", line 353, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.5/urllib2.py", line 499, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 502: Bad Gateway

Indeed, simply trying to load https://edge.launchpad.net/ in a browser gives the same result. Three things to be done:

1. Fix edge.launchpad.net

2. Get +storeblob rolled out to production if it isn't already, so that apport doesn't need to use edge.launchpad.net

3. Fix apport to report errors properly in upload_launchpad_blob (I had to remove a try/except to see this error)

On Wed, Feb 14, 2007 at 02:05:03AM -0000, Robert Collins wrote:
> + apport talks to the 'edge' launchpad server, which is currently disabled
> + because it has a different copy of the database schema than the regular
> + servers. This has occured because we recently deployed a significant set
> + of database patches. Its likely that the apport support in launchpad is
> + now in production and apport should start talking to the production
> + server alias 'launchpad.net' instead of edge.

Yes, apport can switch to using launchpad.net instead of edge now, all
needed functionality and bug fixes have been rolled out to production.

bzr head uses production now. I also fixed the exception displaying.

edge.launchpad.net now works again as well, so I'm closing this task.

 apport (0.55) feisty; urgency=low
 .
   * Add debian/local/ubuntu-bug: Check for a running KDE or Gnome session,
     availability of apport-gtk and -qt, and open the appropriate GUI in bug
     filing mode. This makes it convenient for shell users and is also required
     for proper Firefox 'Report a bug...' menu integration (see bug #85041).
   * debian/apport.install: Install ubuntu-bug to /usr/bin.
   * gtk/apport-gtk: Generously add some gtk.main_iteration() calls to avoid
     hanging dialogs, since we do not have a main loop.
   * apport/ui.py: Do not silently ignore exceptions while uploading data to
     Launchpad, but intercept them and display their message in the error
     dialog. (Part of LP: #84992)
   * apport/ui.py: Switch from edge.launchpad.net to production launchpad.net,
     since the necessary bits are now there. (LP: #84992)