Red Hat Bugzilla – Bug 1094914
libvirt: script and/or trigger should not directly enable systemd units
Last modified: 2014-05-06 13:54:17 EDT
My query script thinks that libvirt has a script or trigger that directly enables a systemd unit using 'systemctl enable'. It probably should not. Please update this packages to use the macroized scriptlet (https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd).
If your package has an exception from FESCo permitting it to enable
itself, please make sure that the service in question is listed in the
appropriate preset file.
There is a general exception described here:
If your package falls under the general exception, then it is possible
that no change is required. Nevertheless, if you are relying on the
exception, please make sure that your rpm scripts are sensible. The
In addition, any service which does not remain persistent on the system (aka, it "runs once then goes away"), does not listen to incoming connections during initialization, and does not require configuration to be functional may be enabled by default (but is not required to do so). An example of "runs once then goes away" service is iptables.
Given that this issue can affect Fedora 20 users who install your
package as a dependency, this bug should be fixed in Fedora 20 and
(In reply to Andy Lutomirski from comment #0)
> My query script thinks that libvirt has a script or trigger that directly
> enables a systemd unit using 'systemctl enable'. It probably should not.
> Please update this packages to use the macroized scriptlet
We already use the macroized scriptlet in F18+ and RHEL7+; your script is picking up a false positive where we wrote our spec file to simultaneously work on RHEL6 where the macros did not exist.
I'm closing this as a dup of bug 850186 that drove our initial conversion to the scriptlet macros in the first place.
*** This bug has been marked as a duplicate of bug 850186 ***
You're right. Sorry for the noise.