[LU-7179] lustre init script output for "status" does not reflect recovery

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.7.0
• Labels: llnl patch
• Severity: 3
• Assignee: Minh Diep
• Reporter: Olaf Faaland

Description

When a target is in recovery, lustre/scripts/lustre produces improper output when run as follows, and a relevant target is in recovery:

/etc/init.d/lustre status
/etc/init.d/lustre status local
/etc/init.d/lustre status foreign

A grep command is invalid, and so always fails, and state is never set to "recovery" regardless of the actual content of lctl get_param -n mdt.*.recovery_status.

The bug was introduced in a commit merged between tags v2_6_52 and v2_6_53,
e3ddff LU-5030 utils: fix hard-coded /proc/fs/lustre in scripts