RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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