Description of problem: Openstack was upgrade from 16.2.3 to 16.2.5 then ffu to 17.1.2 Issues seems to be at one point the domain capabilities in libvirt included ` <flag name='blockdev-reopen.__com.redhat_rhel-av-8_2_0-api'/>` After ffu libvirt is unable to parse the vms with this capability. ~~~ 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api 543496: error : qemuDomainObjPrivateXMLParse:3183 : internal error: Unknown qemu capabilities flag blockdev-reopen.__com.redhat_rhel-av-8_2_0-api ~~~ This cause all the instance to appear as shutdow from libvirt and in turn nova-compute registers the vms as shutdown and then calls the api to set the state to shutdown. Version-Release number of selected component (if applicable): https://access.redhat.com/containers/#/registry.access.redhat.com/rhosp17/openstack-nova-libvirt/images/17.1.2-11.1709628725 [root@compute-10 /]# rpm -qa |grep libvirt libvirt-libs-9.0.0-10.5.el9_2.x86_64 python3-libvirt-9.0.0-1.el9.x86_64 libvirt-client-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-driver-nwfilter-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-driver-secret-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-driver-storage-core-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-driver-qemu-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-driver-nodedev-9.0.0-10.5.el9_2.x86_64 libvirt-daemon-config-nwfilter-9.0.0-10.5.el9_2.x86_64 [root@compute-10 /]# [root@compute-10 /]# rpm -qa |grep qemu qemu-img-7.2.0-14.el9_2.8.x86_64 libvirt-daemon-driver-qemu-9.0.0-10.5.el9_2.x86_64 qemu-pr-helper-7.2.0-14.el9_2.8.x86_64 qemu-kvm-docs-7.2.0-14.el9_2.8.x86_64 ipxe-roms-qemu-20200823-9.git4bd064de.el9_0.noarch qemu-kvm-common-7.2.0-14.el9_2.8.x86_64 qemu-kvm-block-rbd-7.2.0-14.el9_2.8.x86_64 qemu-kvm-device-display-virtio-gpu-7.2.0-14.el9_2.8.x86_64 qemu-kvm-ui-opengl-7.2.0-14.el9_2.8.x86_64 qemu-kvm-ui-egl-headless-7.2.0-14.el9_2.8.x86_64 qemu-kvm-device-display-virtio-gpu-pci-7.2.0-14.el9_2.8.x86_64 qemu-kvm-device-display-virtio-vga-7.2.0-14.el9_2.8.x86_64 qemu-kvm-device-usb-host-7.2.0-14.el9_2.8.x86_64 qemu-kvm-device-usb-redirect-7.2.0-14.el9_2.8.x86_64 qemu-kvm-core-7.2.0-14.el9_2.8.x86_64 qemu-kvm-audio-pa-7.2.0-14.el9_2.8.x86_64 qemu-kvm-tools-7.2.0-14.el9_2.8.x86_64 qemu-kvm-7.2.0-14.el9_2.8.x86_64 How reproducible: Unsure, we do not know what version the flag `blockdev-reopen.__com.redhat_rhel-av-8_2_0-api` is from Actual results: All running instance are show as off and unmanageable Expected results: All running instance are show as on and manageable Additional info:
*** This bug has been marked as a duplicate of bug 2263916 ***