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:
The libvirtd initscript is set to start at priority 97. libvirtd requires that sanlock is already running. sanlock in turn requires that wdmd is already running. Unfortunately both sanlock & wdmd are set to the same priority as libvirtd, 97.

sanlock and wdmd need their priorities changed, so that correct startup ordering is applied. Moving them to sanlock=96,04 and wdmd=95=05 would be sufficient.

Version-Release number of selected component (if applicable):
sanlock-2.3-1.el6.x86_64

How reproducible:


Steps to Reproduce:
1. # grep chkconfig /etc/init.d/wdmd 
2. # grep chkconfig /etc/init.d/sanlock 
  
Actual results:
# chkconfig: 2345 97 03
# chkconfig: 2345 97 03

Expected results:
# chkconfig: 2345 95 05
# chkconfig: 2345 96 04


Additional info:

What role does "Required-Start" play in this?  Does the init script just fail immediately if something listed as required is not started?

# Provides: sanlock
# Required-Start: $time $syslog wdmd

Those comments have little-to-no-effect on the init process itself. IIUC, those comments are only used by tools which configure init. eg if you ask for 'sanlock' to be enabled, the tool would also enable wdmd. It doesn't impact the actual startup ordering AFAIK. The init scripts simply wildcard glob  '/etc/rc?.d/S*' which relies on the numeric priority for sorting.

OK.  I don't know how free we are to change init priorities in an update.  We may have to hack around this in rhel6.

I'm trying to understand if this needs to be fixed for RHEV 3.1.  In a RHEV/VDSM environment, does libvirtd startup require sanlock and wdmd to be running?

This was fixed by only connecting to wdmd when needed, not when started.

*** This bug has been marked as a duplicate of bug 849184 ***