[LU-4751] sanity-hsm test 70, 71 and 72 fails with "Failed to start copytool monitor " Created: 11/Mar/14  Updated: 26/Mar/14  Resolved: 13/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.5.1
Fix Version/s: Lustre 2.6.0, Lustre 2.5.1

Type: Bug Priority: Minor
Reporter: James Nunez (Inactive) Assignee: Michael MacDonald (Inactive)
Resolution: Fixed Votes: 0
Labels: HSM
Environment:

RHEL 6.5 Lustre 2.5.1 RC3 OpenSFS cluster with single MGS/MDS, single OSS with two OSTs, one node running Robinhood, one agent/client and one client


Issue Links:
Related
is related to LU-4020 HSM copytool event monitoring capabil... Resolved
Severity: 3
Rank (Obsolete): 13079

 Description   

Test suite sanity-hsm tests 70, 71 and 72 all fail with

Failed to start copytool monitor on c19

Test logs are at https://maloo.whamcloud.com/test_sets/7f2aafdc-a959-11e3-95fe-52540035b04c



 Comments   
Comment by Peter Jones [ 11/Mar/14 ]

Mike is looking into this

Comment by Michael MacDonald (Inactive) [ 11/Mar/14 ]

Sigh. In dealing with the nuances of running backgrounded processes via mrsh, I inadvertently introduced a hard dependency on it. Environments with -Rssh (or, indeed, any valid non-mrsh $PDSH) shouldn't be using the workaround.

The following fix has been validated to work with -Rmrsh: http://review.whamcloud.com/9587

James, please confirm when possible that the fix also works with -Rssh.

Comment by James Nunez (Inactive) [ 11/Mar/14 ]

Mike,

Your patch works with -Rssh and gets me past the copytool start up.

Thanks.

Comment by Peter Jones [ 13/Mar/14 ]

Landed for 2.5.1 and 2.6

Generated at Sat Feb 10 01:45:32 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.