Re: [PVE-User] Cannot update backup job via API - PVE 6.3.3

Re: [PVE-User] Cannot update backup job via API - PVE 6.3.3

[Fabian Ebner]

Hi,
thanks for the report! I can reproduce this here and will work out a patch.

On 14.01.21 15:25, Mariusz Miodowski via pve-user wrote:
> 
> Hello All,
> 
> We have noticed problem with latest PVE, when trying to update backup job via API.
> 
> It looks that problem is caused by maxfiles parameter. If we omit it, everything works fine.
> 
> This problem is not only related to our environment,  we have already got reports from our clients that they also have the same problem.
> 
> 
> 
> *Request*:
> PUT https://10.10.11.48:8006/api2/json/cluster/backup/3cb1bee67a58e68ea97db1292a23a22a9ea8d529:1
> Array
> (
>     [vmid] => 8001
>     [starttime] => 00:10
>     [maxfiles] => 10
>     [storage] => local
>     [remove] => 1
>     [dow] => tue,wed,sat
>     [mode] => snapshot
>     [compress] => zstd
> )
> 
> 
> *Response*:
> HTTP 500 HTTP/1.1 500 error during cfs-locked 'file-vzdump_cron' operation: value without key, but schema does not define a default key
> Cache-Control: max-age=0
> Connection: close
> Date: Thu, 14 Jan 2021 14:12:37 GMT
> Pragma: no-cache
> Server: pve-api-daemon/3.0
> Content-Length: 13
> Content-Type: application/json;charset=UTF-8
> Expires: Thu, 14 Jan 2021 14:12:37 GMT
> 
> {"data":null}
> 
> 
> -- 
> Regards
> Mariusz Miodowski
> ModulesGarden Development Team Manager
> https://www.modulesgarden.com
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> 

Re: [PVE-User] Cannot update backup job via API - PVE 6.3.3

[Fabian Ebner]

Hi,
a fix for this was applied in git[0] and will become available with the 
next version of pve-manager (but it's not packaged yet).

[0]: 
https://git.proxmox.com/?p=pve-manager.git;a=commit;h=992ff8857d41182edb3e80d005309bccafd95f68

Am 15.01.21 um 13:10 schrieb Fabian Ebner:
> Hi,
> thanks for the report! I can reproduce this here and will work out a patch.
> 
> On 14.01.21 15:25, Mariusz Miodowski via pve-user wrote:
>>
>> Hello All,
>>
>> We have noticed problem with latest PVE, when trying to update backup 
>> job via API.
>>
>> It looks that problem is caused by maxfiles parameter. If we omit it, 
>> everything works fine.
>>
>> This problem is not only related to our environment,  we have already 
>> got reports from our clients that they also have the same problem.
>>
>>
>>
>> *Request*:
>> PUT 
>> https://10.10.11.48:8006/api2/json/cluster/backup/3cb1bee67a58e68ea97db1292a23a22a9ea8d529:1 
>>
>> Array
>> (
>>     [vmid] => 8001
>>     [starttime] => 00:10
>>     [maxfiles] => 10
>>     [storage] => local
>>     [remove] => 1
>>     [dow] => tue,wed,sat
>>     [mode] => snapshot
>>     [compress] => zstd
>> )
>>
>>
>> *Response*:
>> HTTP 500 HTTP/1.1 500 error during cfs-locked 'file-vzdump_cron' 
>> operation: value without key, but schema does not define a default key
>> Cache-Control: max-age=0
>> Connection: close
>> Date: Thu, 14 Jan 2021 14:12:37 GMT
>> Pragma: no-cache
>> Server: pve-api-daemon/3.0
>> Content-Length: 13
>> Content-Type: application/json;charset=UTF-8
>> Expires: Thu, 14 Jan 2021 14:12:37 GMT
>>
>> {"data":null}
>>
>>
>> -- 
>> Regards
>> Mariusz Miodowski
>> ModulesGarden Development Team Manager
>> https://www.modulesgarden.com
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
> 
> 
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> 
>