mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-25 08:55:49 +03:00
[GH-ISSUE #56] System.IndexOutOfRangeException #52
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DerDanilo on GitHub (Dec 6, 2021).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/56
Last working version: v1.11.0
PVE Version: 6.4.x
Thanks for checking!
@franklupo commented on GitHub (Dec 6, 2021):
Hi,
execute with parameter --debug and attach output.
Bets regards
@DerDanilo commented on GitHub (Dec 6, 2021):
Need to test that within the next days. This was on a production system and I cannot break it again to get the output.
What PVE version are you testing against?
@franklupo commented on GitHub (Dec 6, 2021):
The version v1.11.0 is old. If so far the problem is something else. Have you updated Proxmox VE?
Best regards
@DerDanilo commented on GitHub (Dec 6, 2021):
As written before, we are using PVE 6.4.x in the cluster where the error appeared. This cluster cannot be updated at the moment. Please make notes to the tool version if compatibility to specific/older PVE versions ist lost. Thanks!
@franklupo commented on GitHub (Dec 6, 2021):
Compatibility shouldn't be an issue. Try the latest version on a test machine. I use for development 6.4-13. There should be no problem.
@DerDanilo commented on GitHub (Dec 11, 2021):
To answer you question: Of course we will update PVE at a point, we just didn't do it yet.
cv4pve-autosnap: v1.13.2
pveversion: pve-manager/6.4-13/9f411e79 (running kernel: 5.4.143-1-pve)
Here is the debug output, stripped of sensitive data.
@franklupo commented on GitHub (Dec 11, 2021):
Hi,
The problem are the permiss
@DerDanilo commented on GitHub (Dec 11, 2021):
The permission did not change and it was working fine in the past. Apparently the tool now also needs storage.audit permission.
Datastore.Audit VM.Audit VM.Snapshot--> With that it seems to work.Maybe you can improve the output to let the user know that this might be a permission issue, also showing what permissions are required at least.
Also I could not find any information on how to configure the pve snapshot user in your documentation and also not in the Github readme. Can you please add that information?
Thanks!
@franklupo commented on GitHub (Dec 14, 2021):
Hi,
the required permissions are: VM.Audit, VM.Snapshot, Datastore.Audit, Pool.Allocate.
To update the documentation.
Best regards