[GH-ISSUE #22] exit 0 when vm is locked #19

New issue

Closed

opened 2026-02-26 17:43:59 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 17:43:59 +03:00

Owner

Originally created by @GusevVictor on GitHub (Oct 8, 2019).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/22

Hi all. I have use this perfect script. It looks like a very good solution but there is a small problem...

When VM status is locked there is no any kind of altert about it.

For example,

Tru lock a VM like this:

qm set 20009 --lock backup

Run a command like this:

root@osboxes:~# cv4pve-autosnap --host myhost --username root@pam --password=xxx --vmid 20009 snap --label='bar' --keep=2
ACTION Snap 
VMs:   20009
Label: bar 
Keep:  2 
State: False
----- VM 20009 -----
VM 20009 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent
Create snapshot: autobar191008075027
root@osboxes:~# echo $?
0

In cluster log we have an error because vm is locked. There is no create a snap for that vm but script runs without an error...

Please fix that because proxmox can lock vm e.g. during backup, and unlock in again in some cases...

Best regard, Viktor. Thank alot for you job!

Originally created by @GusevVictor on GitHub (Oct 8, 2019). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/22 Hi all. I have use this perfect script. It looks like a very good solution but there is a small problem... When VM status is locked there is no any kind of altert about it. For example, Tru lock a VM like this: `qm set 20009 --lock backup` Run a command like this: ``` root@osboxes:~# cv4pve-autosnap --host myhost --username root@pam --password=xxx --vmid 20009 snap --label='bar' --keep=2 ACTION Snap VMs: 20009 Label: bar Keep: 2 State: False ----- VM 20009 ----- VM 20009 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent Create snapshot: autobar191008075027 root@osboxes:~# echo $? 0 ``` In cluster log we have an error because vm is locked. There is no create a snap for that vm but script runs without an error... **Please fix** that because proxmox can lock vm e.g. during backup, and unlock in again in some cases... **Best regard, Viktor. Thank alot for you job!**

kerem

2026-02-26 17:43:59 +03:00

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@GusevVictor commented on GitHub (Oct 8, 2019):

A small workarround:

 cv4pve-autosnap --host host --username root@pam --password='xxx' --vmid monitor snap --label='bar' --keep=2 --debug|grep 'VM is locked'| while read line ; do echo "FAIL" ; done
 FAIL

You can do any command insted print 'FAIL' word

@GusevVictor commented on GitHub (Oct 8, 2019): A small workarround: ``` cv4pve-autosnap --host host --username root@pam --password='xxx' --vmid monitor snap --label='bar' --keep=2 --debug|grep 'VM is locked'| while read line ; do echo "FAIL" ; done FAIL ``` You can do any command insted print 'FAIL' word

kerem commented

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

Author

Owner

@franklupo commented on GitHub (Oct 8, 2019):

I have handled errors from the task result.
The output will be:

Error in task: VM is locked (backup)

In the coming days I will release the new version.

Best regards

@franklupo commented on GitHub (Oct 8, 2019): I have handled errors from the task result. The output will be: > Error in task: VM is locked (backup) In the coming days I will release the new version. Best regards