[Bug] Unable to modify vm backup task

[buzzzo]

PegaProx version: Beta 0.9.7
Replication type: zfs (proxmox builtin)
Proxmox version: 8.4.1
Installation method: manual
OS/browser: Macos/Chrome
Ui Mode: Corporate
Reverse Proxy: nginx

Step to reproduce:

1. click on: cluster_name -> datacenter -> backup
2. click on backup job and then edit
3. editBackupJob windows comes up
4. try to edit the vm ids by adding new vmid or just click save on the window
5. click save

Expected:
The new vmid should be added

Returned:

error:

When try to modify a backup job created directly in proxmox i receive the following error:

{"errors":{"prune-backups":"invalid format - value without key, but schema does not define a default key\n","next-run":"property is not defined in schema and the schema does not allow additional properties","fleecing":"invalid format - format error\nfleecing.enabled: type check ('boolean') failed - got 'enabled'\n"},"data":null,"message":"Parameter verification failed.\n"}

Screeshot of the error:

[mkellermann97]

Hey @buzzzo — thanks for the report, but the standard bug template didn't come through so I'm missing a chunk of the context I'd usually have. Could you fill in the blanks:

• Installation Method (docker / LXC / manual / …)
• OS and browser you're running the UI in
• UI mode (Modern / Corporate)
• Reverse Proxy? and which one if yes
• Steps to Reproduce — specifically, what did you click before the error popped up? "Edit" on an existing job, "Add" a new one, something else?
• Expected behavior — what should have happened instead?

Also on the screenshot — the error text is cropped on the right. Could you copy the full error as text (from the toast, or the browser devtools console / network response body) so I don't have to OCR it? That's usually what points directly at the failing endpoint.

Re the "VM names vs VMID" note at the bottom — let's track that as #339 so it doesn't get lost inside the bug report.

Self-assigning until the info is in.

[buzzzo]

I've modified my post to align it to template

[mkellermann97]

@buzzzo — apologies for the loop, picking this up late. Fix shipped in v0.9.9 (May 3): PUT /cluster/backup/{id} now strips read-only fields (next-run, last-run-status, …) and converts dict-shaped fields (prune-backups, fleecing, performance) to PVE's property-string format. So 'Parameter verification failed' on edits of jobs created in PVE itself should be gone.

https://github.com/PegaProx/project-pegaprox/releases/tag/v0.9.9.3

If you're past 0.9.9 and still hitting it on a specific backup job, reopen with the cluster_name → datacenter → backup → edit modal and the exact field that fails — that points at a remaining edge case.

https://opencollective.com/pegaprox

— Marcus