From: Cole Robinson <crobinso@redhat.com>
Date: Thu, 21 Nov 2013 20:04:35 +0000 (-0500)
Subject: spec: Don't save/restore running VMs on libvirt-client update
X-Git-Tag: v1.0.5.8~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=390ed2087cd0bbff53e6fab43ef1b859ce9226c9;p=thirdparty%2Flibvirt.git

spec: Don't save/restore running VMs on libvirt-client update

Restarting an active libvirt-guests.service is the equivalent of
doing:

/usr/libexec/libvirt-guests.sh stop
/usr/libexec/libvirt-guests.sh start

Which in a default configuration will managedsave every running VM,
and then restore them. Certainly not something we should do every
time the libvirt-client RPM is updated.

Just drop the try-restart attempt, I don't know what purpose it
serves anyways.

https://bugzilla.redhat.com/show_bug.cgi?id=962225
(cherry picked from commit d65e0e1466b09964b85c79b8cc78be454df53583)
---

diff --git a/libvirt.spec.in b/libvirt.spec.in
index 403b767962..b3f0651e21 100644
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -1630,9 +1630,8 @@ fi
 # If the package is allowed to autostart:
 /bin/systemctl --no-reload enable libvirt-guests.service >/dev/null 2>&1 ||:
 
-# Run these because the SysV package being removed won't do them
+# Run this because the SysV package being removed won't do them
 /sbin/chkconfig --del libvirt-guests >/dev/null 2>&1 || :
-/bin/systemctl try-restart libvirt-guests.service >/dev/null 2>&1 || :
 %endif
 
 %if %{with_sanlock}