Unable to restore S3 backup after upgrading because I'm unable to select the correct bucket

Bug #1804548 reported by Joe Bowen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Won't Fix
Undecided
Unassigned

Bug Description

I'm able to use the dconf-editor to change the deja-dup backend and s3 settings (bucket, key, folder). But when I run Restore, deja-dup reverts the s3 bucket value to a random bucket name. How can I force deja-dup to use the proper bucket name?

Thank you,

Joe

lsb_release -d
Description: Linux Mint 19 Tara

dpkg-query -W deja-dup duplicity
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1

cat /tmp/deja-dup.gsettings
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 's3'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check ''
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'desktop'
org.gnome.DejaDup.S3 id 'AKIAJISLIHF3ETTZY3HQ'
org.gnome.DejaDup.S3 bucket 'deja-dup-auto-akiajkgrripuqo7rcnaa'
org.gnome.DejaDup.S3 folder 'desktop-backup'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'desktop'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'desktop'
org.gnome.DejaDup.Local folder 'desktop'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'desktop'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder 'desktop'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'desktop'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

 cat /tmp/deja-dup.log
DUPLICITY: INFO 1
DUPLICITY: . Using archive dir: /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793

DUPLICITY: INFO 1
DUPLICITY: . Using backup name: 874bc5c99a05b8166bd52ef2053c0793

DUPLICITY: DEBUG 1
DUPLICITY: . GPG binary is gpg, version 2.2.4

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.acdclibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.azurebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.b2backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.botobackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.cfbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.dpbxbackend Failed: No module named dropbox

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.gdocsbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.giobackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.hsibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.hubicbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.imapbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.lftpbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.localbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.mediafirebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.megabackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.multibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ncftpbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.onedrivebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.par2backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.pydrivebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.rsyncbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ssh_paramiko_backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ssh_pexpect_backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.swiftbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.sxbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.tahoebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.webdavbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Main action: collection-status

DUPLICITY: DEBUG 1
DUPLICITY: . Acquiring lockfile /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793/lockfile

DUPLICITY: INFO 1
DUPLICITY: . ================================================================================

DUPLICITY: INFO 1
DUPLICITY: . duplicity 0.7.17 (February 26, 2018)

DUPLICITY: INFO 1
DUPLICITY: . Args: /usr/bin/duplicity collection-status --s3-use-new-style s3+http://deja-dup-auto-akiajislihf3ettzy3hq/desktop-backup --no-encryption --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/jbbowen/.cache/deja-dup --tempdir=/home/jbbowen/.cache/deja-dup/tmp --log-fd=20

DUPLICITY: INFO 1
DUPLICITY: . Linux desktop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64

DUPLICITY: INFO 1
DUPLICITY: . /usr/bin/python 2.7.15rc1 (default, Nov 12 2018, 14:31:15)
DUPLICITY: . [GCC 7.3.0]

DUPLICITY: INFO 1
DUPLICITY: . ================================================================================

DUPLICITY: DEBUG 1
DUPLICITY: . 0 files exist on backend

DUPLICITY: DEBUG 1
DUPLICITY: . 0 files exist in cache

DUPLICITY: DEBUG 1
DUPLICITY: . Extracting backup chains from list of files: []

DUPLICITY: NOTICE 1
DUPLICITY: . Last full backup date: none

DUPLICITY: INFO 3
DUPLICITY: backend BackendWrapper
DUPLICITY: archive-dir (() /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793 dir)
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: BackendWrapper
DUPLICITY: . Archive dir: /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793
DUPLICITY: .
DUPLICITY: . Found 0 secondary backup chains.
DUPLICITY: . No backup chains with active signatures found
DUPLICITY: . No orphaned or incomplete backup sets found.

DUPLICITY: INFO 3
DUPLICITY: backend BackendWrapper
DUPLICITY: archive-dir (() /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793 dir)
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: BackendWrapper
DUPLICITY: . Archive dir: /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793
DUPLICITY: .
DUPLICITY: . Found 0 secondary backup chains.
DUPLICITY: . No backup chains with active signatures found
DUPLICITY: . No orphaned or incomplete backup sets found.

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793/lockfile

DUPLICITY: INFO 1
DUPLICITY: . Using temporary directory /home/jbbowen/.cache/deja-dup/tmp/duplicity-vbb8dc-tempdir

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/jbbowen/.cache/deja-dup/874bc5c99a05b8166bd52ef2053c0793/lockfile

## After running the above command (notice the bucket change) ##

cat /tmp/deja-dup.gsettings
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 's3'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check ''
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'desktop'
org.gnome.DejaDup.S3 id 'AKIAJISLIHF3ETTZY3HQ'
org.gnome.DejaDup.S3 bucket 'deja-dup-auto-akiajislihf3ettzy3hq'
org.gnome.DejaDup.S3 folder 'desktop-backup'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'desktop'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'desktop'
org.gnome.DejaDup.Local folder 'desktop'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'desktop'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder 'desktop'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'desktop'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

Revision history for this message
Michael Terry (mterry) wrote :

Hey sorry for slow reply - worst case, you can use the duplicity command line yourself - you can see it printed out in your report. Just run it manually and replace the bucket name.

I haven’t touched the S3 code in quite a while as it’s deprecated. But we probably shouldn’t be overriding a manually set bucket.

Revision history for this message
Joe Bowen (joe-b-bowen) wrote :

No worries. When I dealt with this issue, I was restoring the S3 backup of my computer that was backed up using deja-dup. Which is why I had to override the S3 bucket setting. However, I did end up just doing what you suggest and manually running the correct duplicity command to restore the backup. We can close this ticket if you want, given that the S3 code has been depreciated. I'll leave the call up to you. Let me know if you need anything from me.

Thank you,

Joe

Revision history for this message
Michael Terry (mterry) wrote :

Ah excellent. I’ll close then, thanks.

Changed in deja-dup:
status: New → Won't Fix
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.