[LU-1798] 2.2.0 Server<->2.3 Client Test failure on test suite lustre-initialization-1, subtest lustre-initialization_1

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.3.0
• Fix Version/s: Lustre 2.3.0, Lustre 2.4.0
• Type: Bug
• Priority: Blocker
• Reporter: Maloo
• Assignee: Niu Yawei (Inactive)
• Resolution: Fixed
• Severity: 3

Description

This issue was created by maloo for sarah <[e-mail]>

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/a526ec14-f127-11e1-bfdc-52540035b04c.

The sub-test lustre-initialization_1 failed with the following error:

Test system failed to start single suite, so abandoning all hope and giving up

08:18:36:08:18:36:CMD: client-20vm3 lctl get_param -n timeout
08:18:36:08:18:36:Using TIMEOUT=20
08:18:37:08:18:37:CMD: client-20vm3 lctl dl | grep ' IN osc ' 2>/dev/null | wc -l
08:18:39:08:18:39:CMD: client-20vm2.lab.whamcloud.com lctl dl | grep ' IN osc ' 2>/dev/null | wc -l
08:18:39:08:18:39:enable jobstats, set job scheduler as procname_uid
08:18:39:08:18:39:CMD: client-20vm3 /usr/sbin/lctl conf_param lustre.sys.jobid_var=procname_uid
08:18:41:08:18:41:client-20vm3: error: conf_param: Invalid argument

Comments

[Andreas Dilger]

The client should check for the jobid connect flag before setting this tunable.

[Niu Yawei (Inactive)]

I think we should set the QUOTA_AUTO as 0 for such interop tests, I'll change the t-f to check lustre version before enabling the jobstats.

[Niu Yawei (Inactive)]

http://review.whamcloud.com/3806

[Peter Jones]

Landed for 2.3 and 2.4