[pve-devel] Issue with CLI, when tried to create backup job

[Thomas Lamprecht]

On 10/8/18 2:58 PM, Eduard Ahmatgareev wrote:
> Does anybody have idea how it possible to fix?
> 

Hi, this problem was reported over other channels too and it seems it was
forgotten to answer yours.. Anyway, a proposed fix is here:
https://pve.proxmox.com/pipermail/pve-devel/2018-October/033992.html

so this is tracked and worked on.

cheers,
Thomas

> 
> чт, 4 окт. 2018 г. в 13:53, Eduard Ahmatgareev <e.ahmatgareev at gmail.com>:
> 
>> Hi,
>>
>> I tried to create new backup job on:
>>
>> root at cluster-13-1:/usr/share/perl5/PVE# pveversion -v
>> proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
>> pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
>> pve-kernel-4.15: 5.2-8
>> pve-kernel-4.15.18-5-pve: 4.15.18-24
>> pve-kernel-4.15.18-4-pve: 4.15.18-23
>> pve-kernel-4.15.17-1-pve: 4.15.17-9
>> corosync: 2.4.2-pve5
>> criu: 2.11.1-1~bpo90
>> glusterfs-client: 3.8.8-1
>> ksm-control-daemon: 1.2-2
>> libjs-extjs: 6.0.1-2
>> libpve-access-control: 5.0-8
>> libpve-apiclient-perl: 2.0-5
>> libpve-common-perl: 5.0-38
>> libpve-guest-common-perl: 2.0-18
>> libpve-http-server-perl: 2.0-11
>> libpve-storage-perl: 5.0-29
>> libqb0: 1.0.1-1
>> lvm2: 2.02.168-pve6
>> lxc-pve: 3.0.2+pve1-2
>> lxcfs: 3.0.2-2
>> novnc-pve: 1.0.0-2
>> proxmox-widget-toolkit: 1.0-20
>> pve-cluster: 5.0-30
>> pve-container: 2.0-27
>> pve-docs: 5.2-8
>> pve-firewall: 3.0-14
>> pve-firmware: 2.0-5
>> pve-ha-manager: 2.0-5
>> pve-i18n: 1.0-6
>> pve-libspice-server1: 0.12.8-3
>> pve-qemu-kvm: 2.11.2-1
>> pve-xtermjs: 1.0-5
>> qemu-server: 5.0-35
>> smartmontools: 6.5+svn4324-1
>> spiceterm: 3.0-5
>> vncterm: 1.5-3
>> zfsutils-linux: 0.7.11-pve1~bpo1
>>
>> with command:
>> pvesh create /cluster/backup --starttime='22:00' --compress='lzo'
>> --dow='sat' --node='cluster-13-1' --storage='images01' --vmid='8470'
>> detected overwriten standard CLI parameter 'quiet'
>> Compilation failed in require at /usr/bin/pvesh line 6.
>> BEGIN failed--compilation aborted at /usr/bin/pvesh line 6.
>>
>> How is it possible to fix?
>> We are using enterprise version