[Bug 1266753] Re: Boto backend removes local cache if connection cannot be made

[Brian Murray]

** Description changed:

+ N.B. This should not be released until after deja-dup - bug 1281066.
+ 
  SRU Justification
- [Impact] 
-  * When there is no connection to the S3 backend, the local cache files are deleted.
+ [Impact]
+  * When there is no connection to the S3 backend, the local cache files are deleted.
  
  [Test Case]
-  1. disable the connection to S3
-  2. run a "collection-status" (basically I run 'duply X status')
+  1. disable the connection to S3
+  2. run a "collection-status" (basically I run 'duply X status')
  
- [Regression Potential] 
-  * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ).
+ [Regression Potential]
+  * Already fixed in latest duplicity. Needs to be fixed in lockstep with deja-dup as it Breaks: deja-dup (<< 27.3.1-0ubuntu2 ).
  
  --
  
  When there is no connection to the S3 backend, the local cache files are
  deleted. To reproduce:
  
  1. disable the connection to S3
  2. run a "collection-status" (basically I run 'duply X status')
  
  You'll get a bunch of these:
  
  Deleting local /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest (not authoritative at backend).
  Deleting local /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz (not authoritative at backend).
  
  This is fatal if you run it in a configuration using GPG and having only
  the public key for encryption as well as a separate signing key. Then
  you cannot backup any more, as the decrypted local cache has been
  deleted and the files on the S3 are encrypted.
  
  Probably reason:
  
  There is no check if the connection to the backend could be established
  
  Workaround:
  
  If you replace at
  
  http://bazaar.launchpad.net/~duplicity-
  team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270
  
  the line
  
      return []
  
  with
  
      return None
  
  Then duplicity will crash instead of deleting the local files. Not the
  proper solution but at least you can do a backup when the connection
  comes back up.

-- 
You received this bug notification because you are a member of Ubuntu
Review Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1266753

Title:
  Boto backend removes local cache if connection cannot be made

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1266753/+subscriptions