Bug or Feature - VM didn't start automaticly when backup go to error

[grefabu]

Hi,

I've change something on my PBS. the conclusion was, that the backup go to error. In this case it was an right problem, but it could be an space problem or somthing else.
For this backup, I set the method to 'Stop', cause I want to 've a full consistent backup with all services down in the virtual machine.

But in cause off the erroe, the backup didn't start the machines automaticly. For me this is an not wanted behavior, but maybee this is a feature not an bug?

Bye

Gregor

 

[dylanw]

Hi,
I tried to replicate this with no success. Could you post the exact error message from the backup?
Does the machine go into a locked state or does it simply power down?
Could you also post the output of pveversion -v?

 

[grefabu]

Hi,

I integrate the Store with the 'wrong' rights for Testing

Then I setup an new backupjob with one VM:

INFO: starting new backup job: vzdump 103 --mailnotification always --all 0 --quiet 1 --storage PH-PBS001_TEST --mode stop --node ph-pve004
INFO: Starting Backup of VM 103 (qemu)
INFO: Backup started at 2021-03-30 15:50:58
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: ph-wc001
INFO: include disk 'virtio0' 'cephpool001:vm-103-disk-0' 32G
INFO: stopping vm
INFO: creating Proxmox Backup Server archive 'vm/103/2021-03-30T13:50:58Z'
INFO: starting kvm to execute backup task
ERROR: VM 103 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam != ph-pvecl001@pbs)
INFO: aborting backup job
INFO: guest is online again after 9 seconds
ERROR: Backup of VM 103 failed - VM 103 qmp command 'backup' failed - backup connect failed: command error: backup owner check failed (root@pam != ph-pvecl001@pbs)
INFO: Failed at 2021-03-30 15:51:07
INFO: Backup job finished with errors
TASK ERROR: job errors

The VM stopped, the Bacup go to error and the VM never will started automaticly.

pveversion -v

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-1-pve: 5.3.18-1
ceph: 14.2.16-pve1
ceph-fuse: 14.2.16-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

 

[dylanw]

Hi,
I was able to reproduce the issue, so opened up a bug report for it [1]. Thanks for reporting!

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=3369

 

[grefabu]

I do waht I could, even it's so less ;-) Thnak you for opening the bug report!