See dependent bug 1946204. This behavior completely breaks RHV. Introduced in f035f53baa2e5dc00b8e866e594672a90b4cea78 and reverted in 32c5e432044689b6679cdedeb1026f27653449d8. Sadly the problem is present in libvirt-7.0.0-11.module+el8.4.0+10505+3a8d753f.x86_64
This issue can be reproduced by below steps(with libvirt-guests), but ovirt doesn't use libvirt-guests, so I think we'd better cover it in RHV integration testing. # cat /etc/sysconfig/libvirt-guests ON_BOOT=ignore ON_SHUTDOWN=shutdown # systemctl start libvirtd # systemctl start libvirt-guests # virsh start avocado-vt-vm1 # systemctl restart libvirtd # virsh list --all Id Name State --------------------------------- - avocado-vt-vm1 shut off
And note that vm should not be set to autostarted: # virsh list --all --autostart Id Name State --------------------
(In reply to Fangge Jin from comment #5) > This issue can be reproduced by below steps(with libvirt-guests), but ovirt > doesn't use libvirt-guests, so I think we'd better cover it in RHV > integration testing. Sorry, my memory is wrong. ovirt uses libvirt-guests: static/usr/lib/systemd/system/vdsmd.service.in:8:Before=libvirt-guests.service
indeed. but we lack a dedicated test for it:/
Test pass with libvirt-7.0.0-13.module+el8.4.0+10604+5608c2b4.x86_64. Same steps as comment5 and comment6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt:av bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2098