Unable to restore S3 backup after upgrading because I'm unable to select the correct bucket
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-
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.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
cat /tmp/deja-dup.log
DUPLICITY: INFO 1
DUPLICITY: . Using archive dir: /home/jbbowen/
DUPLICITY: INFO 1
DUPLICITY: . Using backup name: 874bc5c99a05b81
DUPLICITY: DEBUG 1
DUPLICITY: . GPG binary is gpg, version 2.2.4
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.
DUPLICITY: INFO 1
DUPLICITY: . Main action: collection-status
DUPLICITY: DEBUG 1
DUPLICITY: . Acquiring lockfile /home/jbbowen/
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://
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/
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: BackendWrapper
DUPLICITY: . Archive dir: /home/jbbowen/
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/
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: BackendWrapper
DUPLICITY: . Archive dir: /home/jbbowen/
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/
DUPLICITY: INFO 1
DUPLICITY: . Using temporary directory /home/jbbowen/
DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/jbbowen/
## After running the above command (notice the bucket change) ##
cat /tmp/deja-
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.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
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.