mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-25 17:05:48 +03:00
[GH-ISSUE #66] POSSIBLE PROBLEM PERMISSION #62
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#62
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 @nikitauchaev on GitHub (Jun 13, 2022).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/66
What happened?
Any use of cv4pve-autosnap with any user (including root) crashes with an error:
POSSIBLE PROBLEM PERMISSION 'VM.Audit'
POSSIBLE PROBLEM PERMISSION 'Datastore.Audit'
The required rights have been granted.
Moreover, I repeat, I have already tried to do this as root, the effect is the same.
I tried to recreate the user, roles, assign rights from /, etc., nothing gives effect.
When running with a debug, it gives all the information about nodes, storages and vms.
I transmit the user's username and password explicitly, I do not use tokens.
But I did exactly the same thing all the time before and didn't get any problems. Also, the conclusion of the debag says that all the information is obtained correctly, i.e. the problem is not in the user's authorization.
Expected behavior
At the exit, I would like to get a tool that I have been using for years (by the way, thank you, an excellent utility). To understand what is the reason for such an error and how I can avoid its repetition.
Relevant log output
Proxmox VE Version
7.2-4
Version (bug)
1.14.4
Version (working)
No response
On what operating system are you experiencing the issue?
Linux
Pull Request
@franklupo commented on GitHub (Jun 16, 2022):
Hi,
why use vmid -100 ?
best regards
@franklupo commented on GitHub (Jun 17, 2022):
News?