Backup to Ubuntu one failed, after 5 attempts status 400 bad request
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
duplicity (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Users on Ubuntu 13.04 can't reliably back up to Ubuntu One. Any hiccup in an upload, which is not uncommon with Ubuntu One, will cause a backup failure.
Usually, a hiccup will just cause a retry. But because of this bug, retries will always fail.
[Test Case]
Make a large backup to Ubuntu One. Eventually, you're likely to hit a 400 Bad Request error.
[Regression Potential]
The only change is in the Ubuntu One backend. So regressions will be limited to that.
[Original Report]
On Raring using deja-dup to backup to Ubuntu one, when I add a particular git repository to the folders to backup and then start the backup, the process sits for some minutes at the start of the upload operation and then fails with a popup "Backup Failed. Giving up on request after 5 attempts last status 400 bad request". The progress bar does not get started as far as I can see.
While it is saying that it is uploading I can see in System Monitor that data is being continuously sent, but after the failure there are no new files on U1.
By a process of elimination I determined that it is the objects directory (which itself contains a large number of subdirectories each containing a number of small files) that is causing the problem. I attempted to determine whether it was a particular file or folder that was causing the problem but it seems not to be consistent. I thought that I had found a particular subfolder causing the problem, I cleared .cache/deja_dup, and then it accepted that folder. However when I then put back the rest of the subfolders it failed again.
I copied the complete git repository to another machine (running up to date Ubuntu 12.04) and backing up from there (to a different U1 account) deja_dup has no problems.
I also notice that on Raring it always takes a long time in the verification phase even when only a trivial change has been made. It is as if it is downloading the whole repository, but whether that is a related problem I do not know.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: deja-dup 25.5-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-15-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
Date: Thu Mar 28 20:28:06 2013
InstallationDate: Installed on 2012-08-01 (239 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
MarkForUpload: True
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- edso: Approve
-
Diff: 34 lines (+6/-1)1 file modifiedduplicity/backends/u1backend.py (+6/-1)
- duplicity-team: Pending requested
-
Diff: 27 lines (+7/-3)1 file modifiedduplicity/backends/u1backend.py (+7/-3)
description: | updated |
Changed in duplicity: | |
status: | New → Confirmed |
Changed in duplicity: | |
status: | Confirmed → In Progress |
assignee: | nobody → Christopher Townsend (townsend) |
Changed in duplicity: | |
status: | In Progress → Fix Committed |
Changed in duplicity: | |
assignee: | Christopher Townsend (townsend) → nobody |
importance: | Undecided → Medium |
milestone: | none → 0.6.22 |
status: | In Progress → Fix Committed |
Changed in duplicity (Ubuntu): | |
milestone: | none → raring-updates |
importance: | Undecided → High |
milestone: | raring-updates → none |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.