Restarts fail because comparing long key ID to short key ID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
Using duplicity 0.7.10 on Ubuntu yakkety, when a restart is attempted, I see a failure because the 8 character key ID is being compared against the 16 character key ID. See the relevant part of my log below:
--- Start running command BKP at 16:24:00.197 ---
Reading globbing filelist <snip>/exclude
Synchronising remote metadata to local cache...
Copying duplicity-
Copying duplicity-
Copying duplicity-
Last full backup left a partial set, restarting.
Last full backup date: Fri Oct 7 15:19:21 2016
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
RESTART: Volumes 3 to 3 failed to upload before termination.
Restarting backup at volume 3.
Volume was signed by key 52DA9A50, not 4F07B22452DA9A50
16:25:53.466 Task 'BKP' failed with exit code '22'.
--- Finished state FAILED 'code 22' at 16:25:53.466 - Runtime 00:01:53.269 ---
I was able to edit the configuration, where I replaced all instances of the 8 digit key identifier with a 16 digit identifier, and it worked after that.
It could help, perhaps, to print a more specific error message if the last 8 characters match, but the strings are not identical.