[LU-4707] Don’t deploy the “lustre” init script on clients

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.6.0
• Fix Version/s: Lustre 2.6.0, Lustre 2.5.2
• Type: Bug
• Priority: Major
• Reporter: Malcolm Cowe (Inactive)
• Assignee: Dmitry Eremin (Inactive)
• Resolution: Fixed
• Labels: mn4

Description

The "lustre" init script, etc/rc.d/init.d/lustre, is I think intended for use on Lustre servers only. Can it be removed from the payload for client nodes?

Comments

[Andrea Garcia (Inactive)]

this is a Lustre bug - converting to an LU ticket, per IML triage meeting.

[Dmitry Eremin (Inactive)]

Patch is http://review.whamcloud.com/9535

[Dmitry Eremin (Inactive)]

Patch have landed to master.

[Dmitry Eremin (Inactive)]

patch for b2_5: http://review.whamcloud.com/9940
patch for b2_4: http://review.whamcloud.com/9941

[Andreas Dilger]

Patch landed to b2_5 for 2.5.2.

[Ryan Haasken]

The above change also has the side-effect that the lnet init script will not be included for non-redhat builds due to the "if INIT_SCRIPTS" check in lustre/scripts/Makefile.am.

Why do the init scripts not support a non-redhat environment? As far as I can tell, it actually looks like the lnet init script doesn't use anything from the redhat-specific /etc/rc.d/init.d/functions, and it would work on a SLES machine.

[Dmitry Eremin (Inactive)]

I don't know why those scripts are specific to Red Hat distributive but those scripts are enabled if /etc/init.d/functions and /etc/sysconfig/network files exists.

[Ryan Haasken]

Thanks Dmitry. I've opened LU-5454 to get the lnet init script ported to SLES.

/etc/init.d/functions and /etc/sysconfig/network are specific to RHEL, but as far as I can tell, it's not using anything in /etc/init.d/functions.