0.7.01 S3 upload completely broken in CentOS - ' assert scheme == 's3', AssertionError'

Bug #1423354 reported by Lee W
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

Duplicity version 0.7.01
Python version 2.6.6
OS Distro and version CentOS 6.6
Type of target filesystem: Linux ext3 filesystem

Log output from -v9 option - Include the command line, the first 200 lines of the log, and the last 200 lines of the log:

[root@law-compiletest duplicity-0.7.01]# duplicity -v9 --encrypt-key <mykey> /var/log/ s3+http://mycorp-logs/lxchost/
Using archive dir: /root/.cache/duplicity/0349e9a529be38bd98e5d78714cc86e8
Using backup name: 0349e9a529be38bd98e5d78714cc86e8
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.copycombackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Failed: invalid syntax (onedrivebackend.py, line 172)
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using temporary directory /tmp/duplicity-f4b3Jn-tempdir
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1500, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1494, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1327, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib64/python2.6/site-packages/duplicity/commandline.py", line 1055, in ProcessCommandLine
    backup, local_pathname = set_backend(args[0], args[1])
  File "/usr/lib64/python2.6/site-packages/duplicity/commandline.py", line 948, in set_backend
    globals.backend = backend.get_backend(bend)
  File "/usr/lib64/python2.6/site-packages/duplicity/backend.py", line 221, in get_backend
    obj = get_backend_object(url_string)
  File "/usr/lib64/python2.6/site-packages/duplicity/backend.py", line 207, in get_backend_object
    return factory(pu)
  File "/usr/lib64/python2.6/site-packages/duplicity/backends/_boto_single.py", line 161, in __init__
    self.resetConnection()
  File "/usr/lib64/python2.6/site-packages/duplicity/backends/_boto_single.py", line 183, in resetConnection
    self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)
  File "/usr/lib64/python2.6/site-packages/duplicity/backends/_boto_single.py", line 97, in get_connection
    assert scheme == 's3'
AssertionError

  This is on a freshly installed VM. Per-command provisioning of this VM (from a fairly basic CentOS 6.6 image, provided by Rackspace) can be found here - https://gist.github.com/law/2920145fe65b3154a20d

  The S3 ACLs on the bucket are set wide open, and verified with s3cmd GETs, LSes, and PUTs using the same credentials provided to Duplicity - https://gist.github.com/law/858c55d43f8241a0719c

Revision history for this message
Mjumbe Wawatu Ukweli (mjumbewu) wrote :

I am getting the same traceback on Ubuntu 15.04 with Python 2.7.9.

My last successful backup was apparently 15 days ago, about the time that I updated to 15.04.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

This has been fixed in 0.7.02 and has been released a while back.

Changed in duplicity:
status: New → Fix Released
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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