Better error when S3 password is bad
Bug #307629 reported by
Michael Terry
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Déjà Dup |
Fix Released
|
Medium
|
Michael Terry | ||
Bug Description
Right now, we just say "unknown error" if we can't log into S3. We can do better.
Requires changes to duplicity.
| Changed in deja-dup: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Michael Terry (mterry) wrote | #1 |
| Changed in deja-dup: | |
| assignee: | nobody → mterry |
| milestone: | none → 4.0 |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Fixed by having duplicity 0.5.04 return a special code when it hits an exception (S3 login errors are handled as backend exceptions, oddly). We notice this and throw up a relevant error in 4.0.