B2 backup resume fails for TypeError

Bug #1869921 reported by Brian Wiebe on 2020-03-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Unassigned

Bug Description

Source: Question #689587

Duplicity 0.8.12 on Debian.

Ran initial backup but it terminated prior to finishing. Destination was a B2 bucket in backblaze.

Upon re-running, it found the the backup and processed to restart, but failed due to a TypeError: (note, output has been sanitized)

<host>:~# python2 /usr/local/bin/duplicity /home b2://[account]:[key]@[B2bucket]
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Fri Mar 27 21:43:32 2020
GnuPG passphrase:
Retype passphrase to confirm:
RESTART: Volumes 210 to 211 failed to upload before termination.
         Restarting backup at volume 210.
Attempt 1 failed. TypeError: argument can't be <type 'unicode'>
Attempt 2 failed. TypeError: argument can't be <type 'unicode'>
Attempt 3 failed. TypeError: argument can't be <type 'unicode'>
Attempt 4 failed. TypeError: argument can't be <type 'unicode'>
Giving up after 5 attempts. TypeError: argument can't be <type 'unicode'>
<host>:~#

Brian Wiebe (bwiebe) wrote :

output with -v9 (note: it has been sanitized)

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

Other bug subscribers

Related questions

Bug attachments