From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Cannot update backup job via API - PVE 6.3.3
Date: Fri, 29 Jan 2021 10:07:37 +0100 [thread overview]
Message-ID: <198f74ad-1840-e895-6c11-3c6271fac643@proxmox.com> (raw)
In-Reply-To: <7adad43c-3f8a-62d5-9b84-fae6ea1d57b3@proxmox.com>
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
>
>
prev parent reply other threads:[~2021-01-29 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.507.1610638097.344.pve-user@lists.proxmox.com>
2021-01-15 12:10 ` Fabian Ebner
2021-01-29 9:07 ` Fabian Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=198f74ad-1840-e895-6c11-3c6271fac643@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.