https://bugzilla.redhat.com/show_bug.cgi?id=1195882 Force re-reading of the capabilities cache upon new installations. Since re-reading of the capabilities is based on the 'ctime' of either the QEMU binary or if the new libvirtd is greater than what created the cache file, it's possible that depending on the order of installations that a later date created "backported" libvirtd could create the cache file while followup installation of a mainline release that had an earlier creation date wouldn't cause the cache to be updated. This results in the possibility that (a) feature(s) in the mainstream release wouldn't be available unless someone delete the cache by hand. Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> --- libvirt.spec.in | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/libvirt.spec.in b/libvirt.spec.in index 4195518..e28f737 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -1705,6 +1705,10 @@ fi /sbin/chkconfig --add virtlockd %endif +# Remove any files in the capabilities cache to force the daemon +# to start fresh +rm -rf %{_localstatedir}/cache/libvirt/qemu/capabilities + %preun daemon %if %{with_systemd} %if %{with_systemd_macros} @@ -1828,6 +1832,13 @@ exit 0 %endif %endif %endif + +%post daemon-driver-qemu + +# Remove any files in the capabilities cache to force the daemon +# to start fresh +rm -rf %{_localstatedir}/cache/libvirt/qemu/capabilities + %endif # %{with_libvirtd} %preun client -- 2.1.0 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list