v1.2.1
Patch release for #51.
Fixed
- A sync route that pulls now tells PBS who owns the backups it fetches, namely the API token Joulenap uses on the receiving server. Without that field PBS falls back to
root@pam, and the run fails on every group with "owner check failed" as soon as the target datastore already holds backups owned by the token, which is the normal state of any datastore Joulenap itself backs up to (#51). Push routes were never affected: pushed backups belong to the account named in the remote configuration, whatever the job asks for.
Upgrading
A pull route that ran before this fix wrote its groups on the target as root@pam, so the first run afterwards reports the same owner mismatch the other way round. Reassign those groups once on the receiving server, with Change Owner in the datastore's Content tab or with proxmox-backup-client change-owner.
Docker
catubba/joulenap:1.2.1 (also :latest), digest sha256:e86063e8ae6648df1e7a8f621fbe7775976509153c153c0d19e98a5baf8248b4.
Full changelog: https://github.com/Joulenap/joulenap/blob/main/CHANGELOG.md