Hide Forgot
Description of problem: libvirtd is configured as "conflicting service" in vdsmd init-script. that way vdsmd stops libvirtd process if its running via sysVinit script, and then run in with the upstart project, to do so, it checks with `service libvirtd status`. The problem is `service libvirtd status` response true also if it runs via the upstart job. that way vdsmd *always* restarts libvirtd upon startup. instead vdsmd should also check if ! /sbin/initctl stauts libvirtd 2> /dev/null and only then stop it. Version-Release number of selected component (if applicable): vdsm-4.9-96.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
shutdown_conflicting_srv() { local srv for srv in $CONFLICTING_SERVICES do /sbin/chkconfig $srv off if /sbin/service $srv status > /dev/null 2>&1; then if [ "$srv" == "libvirt-guests" ]; then /bin/rm -f /var/lock/subsys/libvirt-guests + elif [ "$srv" == "libvirtd" ] & + ! /sbin/initctl stauts $srv 2> /dev/null; then + continue else /sbin/service $srv stop fi fi done return 0 }
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
suggest patch: http://gerrit.ovirt.org/#/c/7331/
ok - vdsm-4.9.6-34.0.el6_3.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1508.html