[SOLVED] VZdump Hook problem after last update

[Chriswiss]

Hello,

Yesterday I made the following upgrades:

2020-07-13 07:31:31 upgrade libavfilter7:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:31 upgrade libswscale5:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:31 upgrade libavformat58:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:32 upgrade libavcodec58:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:32 upgrade libswresample3:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:32 upgrade libpostproc55:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:32 upgrade libavutil56:amd64 7:4.1.4-1~deb10u1 7:4.1.6-1~deb10u1
2020-07-13 07:31:32 upgrade libproxmox-backup-qemu0:amd64 0.1.7-1 0.6.1-1
2020-07-13 07:31:33 upgrade libpve-storage-perl:all 6.1-8 6.2-3
2020-07-13 07:31:33 upgrade libpve-guest-common-perl:all 3.0-10 3.0-11
2020-07-13 07:31:33 upgrade libpve-common-perl:all 6.1-3 6.1-5
2020-07-13 07:31:33 upgrade libpve-access-control:all 6.1-1 6.1-2
2020-07-13 07:31:33 upgrade libpve-http-server-perl:all 3.0-5 3.0-6
2020-07-13 07:31:33 upgrade libruby2.5:amd64 2.5.5-3+deb10u1 2.5.5-3+deb10u2
2020-07-13 07:31:33 upgrade proxmox-widget-toolkit:all 2.2-8 2.2-9
2020-07-13 07:31:33 upgrade pve-container:all 3.1-8 3.1-10
2020-07-13 07:31:35 upgrade pve-qemu-kvm:amd64 5.0.0-4 5.0.0-9
2020-07-13 07:31:37 upgrade qemu-server:amd64 6.2-3 6.2-8
2020-07-13 07:31:38 upgrade pve-manager:amd64 6.2-6 6.2-9
2020-07-13 07:31:38 upgrade ruby2.5:amd64 2.5.5-3+deb10u1 2.5.5-3+deb10u2

I use a hook script to send my backups to external storage via rclone.

In this script, I use a TARFILE variable and it seems not to exist anymore.

There has been a change in the environment variables for VZdump ?

Best.
CG

 

[Stoiko Ivanov]

In this script, I use a TARFILE variable and it seems not to exist anymore.

Please try with TARGET - there was a commit recently which change the name
if it works it would be great if you report back here

Thanks!

 

[Chriswiss]

Please try with TARGET - there was a commit recently which change the name
if it works it would be great if you report back here

Thanks!

Great, thanks, that's fine, it works with TARGET.

 

[Stoiko Ivanov]

Thanks for reporting the issue (and confirming the fix)!

I sent a patch for discussion to our mailing-list:
https://lists.proxmox.com/pipermail/pve-devel/2020-July/044353.html

In any case the variable got renamed and keeping it at TARGET is future proof

 

[Chriswiss]

Thanks for reporting the issue (and confirming the fix)!

I sent a patch for discussion to our mailing-list:
https://lists.proxmox.com/pipermail/pve-devel/2020-July/044353.html

In any case the variable got renamed and keeping it at TARGET is future proof

Thank you for the fast service!