"bzr push" failing with SubversionException: OPTIONS request failed

Bug #255159 reported by Eric P. Mangold
4
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Fix Released
Low
Jelmer Vernooij

Bug Description

I've used the svn plugin in exactly this fashion before on the same server and with the same repository without any issues. It's been several weeks since I last pushed, and now it always fails with the following exception:

% bzr push
Using saved location: svn+https://svn2.hosted-projects.com/Phoenix/PCP/branches/fxcm-3
bzr: ERROR: libsvn._core.SubversionException: ("OPTIONS request failed on '/Phoenix/PCP/branches'", 175002)

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 834, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 790, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 492, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 776, in run
    make_directory, to_transport, redirected)
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/__init__.py", line 1664, in do_catching_redirections
    return action(transport)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 768, in make_directory
    transport.mkdir('.')
  File "/usr/lib/python2.5/site-packages/bzrlib/plugins/svn/errors.py", line 119, in convert
    raise convert_error(e)
SubversionException: ("OPTIONS request failed on '/Phoenix/PCP/branches'", 175002)

bzr 1.3.1 on python 2.5.2.final.0 (linux2)
arguments: ['/usr/bin/bzr', 'push']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
  bzrtools /usr/lib/python2.5/site-packages/bzrlib/plugins/bzrtools [1.3.0]
  launchpad /usr/lib/python2.5/site-packages/bzrlib/plugins/launchpad [unknown]
  svn /usr/lib/python2.5/site-packages/bzrlib/plugins/svn [0.4.9]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.

Related branches

Revision history for this message
Eric P. Mangold (teratorn) wrote :

I just tried this push again (right now) and it worked! I haven't touched my repo since reporting this bug, and I haven't touched my installed copy of bzr either.

The server I'm pushing to is not under my control, and it seems likely that this bug is related to some server-side behavior difference between now when I tried to push these revisions initially. I don't have any idea what that could be, however.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Thanks for the update, I'm closing this bug for now. Please reopen if it persists.

Changed in bzr:
status: New → Invalid
Revision history for this message
Eric P. Mangold (teratorn) wrote :

Well... I would say it's still a bug, in the sense that if this behavior is indeed caused by a server-side malfunction then bzr ought to report that information in a more friendly way, as opposed to a stacktrace. Feel free to close it again if you disagree.

Changed in bzr-svn:
status: Invalid → New
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I agree :-) I changed bzr-svn earlier this evening to not show a traceback, but just a single line, e.g.:

bzr: ERROR: OPTIONS request failed on '/Phoenix/PCP/branches'

I'm afraid there's not much more I can do - the error message comes from the Subversion library that bzr-svn uses, and it's error messages are unfortunately very cryptic :-(

Revision 1680 in the 0.4 branch.

Changed in bzr-svn:
assignee: nobody → jelmer
importance: Undecided → Low
milestone: none → 0.4.12
status: New → Fix Committed
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
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

Remote bug watches

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