We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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!
The text was updated successfully, but these errors were encountered:
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
Sorry, something went wrong.
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
Fix #23, #22, #20, #19
f096973
No branches or pull requests
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:
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!
The text was updated successfully, but these errors were encountered: