Wind River Support Network

HomeDefectsOVP-863

Fixed

OVP-863 : the sanlock recipe doesn't arrange to start sanlock at boot

Created: Aug 7, 2013 Updated: Mar 11, 2016

Resolved Date: Sep 2, 2013

Found In Version: 5.0.1

Fix Version: 5.0.1.7

Severity: Low

Applicable for: Wind River Linux 5

Component/s: Userspace

Description

The sanlock recipe contains the following code:

  inherit update-rc.d pythonnative python-dir useradd

  #start wdmd first
  INITSCRIPT_NAME = "sanlock"
  INITSCRIPT_PARAMS = "defaults 21"
  INITSCRIPT_NAME = "wdmd"
  INITSCRIPT_PARAMS = "defaults"

The second pair of initializations overwrite sthe first pair; hence wdmd is added to the list of init scripts, but not sanlock.  This code needs to use the INITSCRIPT_PACKAGES feature, and set INITSCRIPT_NAME_${PN} (etc.).  See ovirt-node_git.bb for an example of how this works.

Workaround

Fortunately, the vdsm daemon will start sanlock if it isn't already running.

Steps to Reproduce

.../configure --enable-board=intel-xeon-core --enable-kernel=preempt-rt+xfs --enable-rootfs=ovp-ovirt-node+third-party-engine+gdb --enable-addons=wr-ovp ...
make all

Observe in export/dist/etc/rc.3 that we have S20wdmd but no equivalent file for sanlock.