[LU-7072] sanityn test_78: Expected set_param to return 0 or EAGAIN

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.8.0
• Severity: 3
• Assignee: Henri Doreau (Inactive)
• Reporter: Maloo

Description

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

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/7cec4ac6-4f04-11e5-bc53-5254006e85c2.

The sub-test test_78 failed with the following error:

CMD: shadow-21vm3 lctl set_param ost.OSS.ost_io.nrs_policies=orr
CMD: shadow-21vm3 lctl set_param ost.OSS.*.nrs_orr_quantum=1
shadow-21vm3: error: set_param: setting ost.OSS.ost_io.nrs_orr_quantum=1: No such device
ost.OSS.ost_io.nrs_orr_quantum=1
 sanityn test_78: @@@@@@ FAIL: Expected set_param to return 0 or EAGAIN

This may relate to the recently landed patch:
http://review.whamcloud.com/15104 "LU-6673 ptlrpc: Forbid too early NRS policy tunings"

This just started on Aug 30, and all patches failing so far are based on either:
LU-6667 llite: improve ll_getname
LU-6903 lov: call lov_object_find_cbdata() inside lock

Info required for matching: sanityn 78

Issue Links

• is related to: LU-7105 sanityn test_28 fails with 'error() without useful message, please fix'
• is related to: LU-7096 Unprotected critical section in nrs_policy_stop
• is related to: LU-7310 sanityn test_39a fails with 'mtime is not updated on write: 1444890978 <= 1413354977 <= 1444890979'
• is related to: LU-6673 NRS crash when applying tunings