starred/cv4pve-autosnap

Fork 0

mirror of https://github.com/Corsinvest/cv4pve-autosnap.git synced 2026-04-25 08:55:49 +03:00

[GH-ISSUE #59] incorrect msg: Storage over 95%, no snapshot taken #55

New issue

Closed

opened 2026-02-26 17:44:11 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 17:44:11 +03:00

Owner

Originally created by @lifeboy on GitHub (Jan 12, 2022).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/59

What happened?

I created a user (snapshot@pve) with the rights needed: VM.Snapshot, Pool.Allocate, VM.Audit, Datastore.Audit

# /usr/local/bin/cv4pve-autosnap --host=192.168.131.1 --username="snapshot@pve" --password="cameraman" --vmid=104 snap --label="daily" --keep=6
ACTION Snap
VMs:              104
Label:            daily
Keep:             6
State:            False
Timeout:          30000
Timestamp format: yyMMddHHmmss
Max % Storage :   95%
----- POSSIBLE PROBLEM PERMISSION 'Datastore.Audit' -----
----- VM 104 Lxc -----
Skip VM problem storage space out of 95%
Total execution 00:00:00.2640291

Why is there a "POSSIBLE PROBLEM PERMISSION 'Datastore.Audit'" message?

more importantly, I have around 50% free storage in my ceph cluster of around 30TB.

Proxmox 6.4-13

Expected behavior

I expect the snapshots to be made.

Relevant log output

No response

Proxmox VE Version

6.4.13

Version (bug)

1.13.3

Version (working)

No response

On what operating system are you experiencing the issue?

Linux

Pull Request

I would like to do a Pull Request

Originally created by @lifeboy on GitHub (Jan 12, 2022). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/59 ### What happened? I created a user (snapshot@pve) with the rights needed: VM.Snapshot, Pool.Allocate, VM.Audit, Datastore.Audit ``` # /usr/local/bin/cv4pve-autosnap --host=192.168.131.1 --username="snapshot@pve" --password="cameraman" --vmid=104 snap --label="daily" --keep=6 ACTION Snap VMs: 104 Label: daily Keep: 6 State: False Timeout: 30000 Timestamp format: yyMMddHHmmss Max % Storage : 95% ----- POSSIBLE PROBLEM PERMISSION 'Datastore.Audit' ----- ----- VM 104 Lxc ----- Skip VM problem storage space out of 95% Total execution 00:00:00.2640291 ``` Why is there a "POSSIBLE PROBLEM PERMISSION 'Datastore.Audit'" message? more importantly, I have around 50% free storage in my ceph cluster of around 30TB. Proxmox 6.4-13 ### Expected behavior I expect the snapshots to be made. ### Relevant log output _No response_ ### Proxmox VE Version 6.4.13 ### Version (bug) 1.13.3 ### Version (working) _No response_ ### On what operating system are you experiencing the issue? Linux ### Pull Request - [ ] I would like to do a Pull Request

kerem

2026-02-26 17:44:11 +03:00

closed this issue
added the
needs investigation
label

kerem commented

2026-02-26 17:44:12 +03:00

Author

Owner

@franklupo commented on GitHub (Jan 12, 2022):

Hi,
the message "POSSIBLE PROBLEM PERMISSION 'Datastore.Audit'" is show when the result of total space is zero. Your user have a 'Datastore.Audit' permission?

Best regards

@franklupo commented on GitHub (Jan 12, 2022): Hi, the message "POSSIBLE PROBLEM PERMISSION 'Datastore.Audit'" is show when the result of total space is zero. Your user have a 'Datastore.Audit' permission? Best regards

kerem commented

2026-02-26 17:44:12 +03:00

Author

Owner

@lifeboy commented on GitHub (Jan 13, 2022):

Here is the role directly from the interface:

The user has that role.

I'm going to remove it and add it again to see if it works.

@lifeboy commented on GitHub (Jan 13, 2022): Here is the role directly from the interface: ![image](https://user-images.githubusercontent.com/4822951/149312193-c8115f6b-cd16-4d73-bada-68da74ff5792.png) The user has that role. I'm going to remove it and add it again to see if it works.

kerem commented

2026-02-26 17:44:12 +03:00

Author

Owner

@lifeboy commented on GitHub (Jan 13, 2022):

I recreated it and it still didn't work. Then I changed the user permission to have access to / instead of /vms and that solved the problem.

@lifeboy commented on GitHub (Jan 13, 2022): I recreated it and it still didn't work. Then I changed the user permission to have access to `/` instead of `/vms` and that solved the problem.

kerem commented

2026-02-26 17:44:12 +03:00

Author

Owner

@matze0301 commented on GitHub (Dec 20, 2023):

I recreated it and it still didn't work. Then I changed the user permission to have access to / instead of /vms and that solved the problem.

I had the same problem and your solution worked for me too.

Thank You!

@matze0301 commented on GitHub (Dec 20, 2023): > I recreated it and it still didn't work. Then I changed the user permission to have access to `/` instead of `/vms` and that solved the problem. I had the same problem and your solution worked for me too. Thank You!