An unexpected error has occurred while updating a Launchpad branch

Bug #1035338 reported by chrisrogers1234
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Critical
Unassigned

Bug Description

I received the following message while attempting a commit:

Committing to: bzr+ssh://bazaar.launchpad.net/~chris-rogers/maus/devel_2/
modified src/common_py/ConfigurationDefaults.py
Committed revision 792.
<Fault 380: 'An unexpected error has occurred while updating a Launchpad branch. Please report a Launchpad bug and quote: OOPS-bb5e548a4d345b909e63c62f79dfc551.'>
"<Fault 380: 'An unexpected error has occurred while updating a Launchpad branch. Please report a Launchpad bug and quote: OOPS-bb5e548a4d345b909e63c62f79dfc551.'>"

bzr version is (bzr --version):

Bazaar (bzr) 2.4.1
  Python interpreter: /usr/bin/python 2.7.2
  Python standard library: /usr/lib/python2.7
  Platform: Linux-3.0.0-12-generic-x86_64-with-LinuxMint-12-lisa
  bzrlib: /usr/lib/python2.7/dist-packages/bzrlib
  Bazaar configuration: /home/cr67/.bazaar
  Bazaar log file: /home/cr67/.bzr.log

Copyright 2005-2011 Canonical Ltd.
http://bazaar.canonical.com/

bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.

Bazaar is part of the GNU Project to produce a free operating system.

Tags: timeout
Revision history for this message
chrisrogers1234 (chris-rogers) wrote :

A bit more info - the bzr command I ran was:

bzr commit -m 'Add neutrinos to kill list' src/common_py/ConfigurationDefaults.py

bzr info reports

Checkout (format: 2a)
Location:
       checkout root: .
  checkout of branch: bzr+ssh://bazaar.launchpad.net/~chris-rogers/maus/devel_2/

Related branches:
    push branch: bzr+ssh://bazaar.launchpad.net/~chris-rogers/maus/devel_2/
  submit branch: bzr+ssh://bazaar.launchpad.net/%2Bbranch/maus/
cr67@ctr ~/MAUS/maus_rogers_devel $

Revision history for this message
Martin Packman (gz) wrote :

Do you have the same issue if you work in local branch then push, rather than committing a lightweight checkout? That's not a typical way of using launchpad code hosting.

Revision history for this message
John A Meinel (jameinel) wrote :
Download full text (4.0 KiB)

The OOPS did end up loading (eventually) for me with:
  Fault: <Fault -1: 'OOPS-394216d625e87559cda9d8b92d70b90f'>

    Traceback (most recent call last):
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/lib/lp/services/twistedsupport/__init__.py", line 139, in wrapped
    return func(*args, **kwargs)
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/lib/lp/codehosting/vfs/branchfs.py", line 686, in got_path_info
    data['id'], **info)
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/lib/lp/codehosting/vfs/branchfsclient.py", line 123, in branchChanged
    repository_string)
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/lib/lp/services/twistedsupport/xmlrpc.py", line 50, in callRemote
    method_name, *args, **kwargs)
--- <exception caught here> ---
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/eggs/Twisted-11.1.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py", line 134, in maybeDeferred
    result = f(*args, **kw)
  File "/srv/bazaar.launchpad.net/production/codehosting2-rev-15505/lib/lp/services/twistedsupport/xmlrpc.py", line 35, in callRemote
    return getattr(self._proxy, method_name)(*args, **kwargs)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "/usr/lib/python2.6/xmlrpclib.py", line 1253, in request
    return self._parse_response(h.getfile(), sock)
  File "/usr/lib/python2.6/xmlrpclib.py", line 1392, in _parse_response
    return u.close()
  File "/usr/lib/python2.6/xmlrpclib.py", line 838, in close
    raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault -1: 'OOPS-394216d625e87559cda9d8b92d70b90f'>

And following that OOPS I get:
RequestExpired: request expired.

    Traceback (most recent call last):
  Module zope.publisher.publish, line 134, in publish
    result = publication.callObject(request, obj)
  Module lp.services.webapp.publication, line 458, in callObject
    return mapply(ob, request.getPositionalArguments(), request)
  Module zope.publisher.publish, line 109, in mapply
    return debug_call(obj, args)
   - __traceback_info__: <security proxied zope.app.publisher.xmlrpc.metaconfigure.CodehostingAPI instance at 0x14871ad0>
  Module zope.publisher.publish, line 115, in debug_call
    return obj(*args)
  Module lp.code.xmlrpc.codehosting, line 289, in branchChanged
    return run_with_login(login_id, branch_changed)
  Module lp.code.xmlrpc.codehosting, line 111, in run_with_login
    requester = getUtility(IPersonSet).get(login_id)
  Module lp.registry.model.person, line 3602, in get
    return Person.get(personid)
  Module storm.sqlobject, line 321, in get
    obj = store.get(cls, id)
  Module storm.store, line 178, in get
    result = self._connection.execute(select)
  Module storm.databases.postgres, line 266, in execute
    return Connection.execute(self, statement, params, noresult)
  Module storm.database, line 238, in execute
    raw_cursor = self.raw_execute(statement, params)
  Module storm.databases.postgres, line 276, in raw_execute
    return Connec...

Read more...

tags: added: timeout
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
chrisrogers1234 (chris-rogers) wrote :

> Do you have the same issue if you work in local branch then push, rather than committing a lightweight checkout? That's not a
> typical way of using launchpad code hosting.

In fact I only got the issue as a one-off, it seems okay now.

Yeah, I come from cvs so I am used to just doing cvs commit -m 'Blah', don't really see the point of all this mucking about with push/pull/branch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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