Majic Projects
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Closed Bug report MAR-121 Backups do not work due long key ID used in Duply configuration on Debian Jessie when deploying with Ansible 2.x
Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
  • Targetted for
  • Status
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    2 hours
  • Time spent
    1 hour
    Click here to see time logged against this issue
Issue details
  • Resolution
  • Reproducability
  • Severity
    Not determined
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates

When provisioning backup client on a Debian Jessie server using Ansible 2.x, the backups do not work due to long key ID use in Duply configuration (the cutoff not being correctly done during key ID extraction). In case of Debian Jessie, it is necessary to supply short key ID (in Stretch long key ID is expected).

The issue seems to come from weird interpolation issue in Ansible 2.x. This might be a good candidate to test in a separate instance and report upstream.

The way to resolve this is to update backup_client/defaults/main.yml to exclude the curly brackets around backup_client_gnupg_details.cutoff variable, and instead add the brackets directly within Extract encryption key identifier (Duplicty requires key ID in hexadecimal format) and Extract additional encryption keys identifiers (Duplicty requires key ID in hexadecimal format).

Steps to reproduce this issue

Reproduction steps:

  1. Deploy backup_server role on any server.

  2. Deploy backup_client role on a Debian Jessie server using Ansible 2.x.

  3. Login into the machine and run the backup:

sudo duply main backup

Expected results:

  1. Backup run succeeds without errors.

Actual results:

  1. Backup run fails with the following error:

    --- Start running command BKP at 10:32:57.162 ---
    Sign key should be an 8 character hex string, like 'AA0E73D2'.
    Received 'F66FFBD83290556A' instead.
    10:32:57.245 Task 'BKP' failed with exit code '10'.
    --- Finished state FAILED 'code 10' at 10:32:57.245 - Runtime 00:00:00.082 ---
Comments ()
There are no comments