On 10/07/2016 05:04 PM, Andrea Bolognani wrote:
On Fri, 2016-10-07 at 11:42 +0200, Andrea Bolognani wrote:
On Fri, 2016-10-07 at 11:19 +0200, Boris Fiuczynski wrote:
Andrea, there is another "side effect" of the Requires directive. libvirt-guests gets automatically started when libvirt is updated to v2.3.0. This has some rather nasty implications for the end users.
Mh, I don't see why that would happen.
The Requires relationship goes in the opposite direction, so if libvirt-guests was not running before the upgrade there should be no reason for it to be started, whether that relationship is there or not.
I'll try to reproduce this on my machine and get back to you in a while.
I tried upgrading from 2.2.0 to 2.3.0 a bunch of times, but I haven't been able to reproduce the failure you're reporting: libvirt-guests is never started automatically.
Can you provide more information? What distribution are you using? Are you building from source, or using your distribution's packages? Are you sure libvirt-guests was not running even before upgrade?
-- Andrea Bolognani / Red Hat / Virtualization
I used fc20 and built the libvirt rpms from source. libvirt-guests was not running when updating from 2.2.0 to libvirt 2.3.0. I switched systems and retried on fc23 after rebuilding libvirt 2.2.0 and 2.3.0 from source. On this system I cannot reproduce the behaviour. You are correct that the behaviour I got does not match with the requires directive. So my guess is that my old fc20 might still have some systemd problem which has been fixed in newer fc versions. -- Mit freundlichen Grüßen/Kind regards Boris Fiuczynski IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martina Köderitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294