OOPS-1601D3000 trying to convert bug reports to questions

[Bryce Harrington]

[Problem]
Launchpad errors when trying to move bug reports to answers, when including text in the comment field. (Problem often still occurs when leaving comment field blank as well, but not always.)

[Discussion]
I've noticed this issue for quite some time, on a range of different bug reports against Ubuntu, on source packages like xorg, xserver-xorg-video-intel, xorg-server, and the like. When I put text in the comment field and submit, Launchpad never succeeds in converting it to answers, instead timing out and giving an error message. Sometimes it also shows an Oops, but not always. Here is one I got when testing this with bug 572818:

Timeout error

Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

Trying again in a couple of minutes might work.

(Error ID: OOPS-1601D3000)

Traceback (most recent call last):

    * Module zope.publisher.publish, line 134, in publish
    * Module canonical.launchpad.webapp.publication, line 428, in callObject
      return mapply(ob, request.getPositionalArguments(), request)
    * Module zope.publisher.publish, line 109, in mapply
      __traceback_info__: <security proxied zope.browserpage.metaconfigure.SimpleViewClass from /srv/launchpad.net/production/launchpad-rev-9342/lib/lp/bugs/browser/../templates/bug-create-question.pt instance at 0x2aaac461ed90>
    * Module zope.publisher.publish, line 115, in debug_call
    * Module canonical.launchpad.webapp.publisher, line 274, in __call__
      self.initialize()
    * Module canonical.launchpad.webapp.launchpadform, line 111, in initialize
      self.form_result = action.success(data)
    * Module zope.formlib.form, line 606, in success
    * Module lp.bugs.browser.bugtask, line 3602, in create_action
      self.context.bug.convertToQuestion(self.user, comment=comment)
    * Module lp.bugs.model.bug, line 1070, in convertToQuestion
      content=comment)
    * Module lp.bugs.model.bug, line 824, in newMessage
      msg, bugwatch, remote_comment_id=remote_comment_id)
    * Module lp.bugs.model.bug, line 835, in linkMessage
      if message not in self.messages:
    * Module storm.sqlobject, line 551, in __contains__
    * Module storm.sqlobject, line 505, in _result_set
    * Module storm.sqlobject, line 489, in _finish_result_set
    * Module storm.sqlobject, line 483, in _prepare_result_set
    * Module storm.store, line 206, in find
    * Module storm.store, line 486, in flush
    * Module storm.store, line 548, in _flush_one
    * Module storm.databases.postgres, line 249, in execute
    * Module storm.database, line 217, in execute
    * Module storm.databases.postgres, line 259, in raw_execute
    * Module storm.database, line 303, in raw_execute
    * Module storm.database, line 342, in _check_disconnect
    * Module storm.tracer, line 95, in trace
    * Module canonical.launchpad.webapp.adapter, line 483, in connection_raw_execute_error
      raise LaunchpadTimeoutError(statement, params, error)

LaunchpadTimeoutError: Statement: 'UPDATE BugTask SET date_closed=%s, date_left_new=%s, status=%s WHERE BugTask.id = %s'<br /> Parameters:[<storm.variables.DateTimeVariable object at 0x2aaaace25350>, <storm.variables.DateTimeVariable object at 0x10b9e3d0>, <canonical.database.enumcol.DBEnumVariable object at 0xd977650>, <storm.variables.IntVariable object at 0xc1bf410>]<br /> Original error: QueryCanceledError('canceling statement due to statement timeout\n',)<br />

This oops was obtained when filing against the production server; if I try running it against edge I get a generic timeout error message but no oops.

seb128 had indicated he does bug->q quite often and hasn't seen this problem, but he never gives comments on them. I find that at least a couple times this worked for me, but not reliably, and it is not working right now. Even if the comment field is blank it times out. So that makes me wonder if it's something particular to either X packages or to my account.

I installed launchpad locally and tried testing using the test account, and was not able to reproduce the error there.