[LU-9669] sanityn test_77e: @@@@@@ FAIL: failed to set TBF policy

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.11.0
• Type: Bug
• Priority: Minor
• Reporter: VIKRAM BABASO JADHAV (Inactive)
• Assignee: WC Triage
• Resolution: Fixed
• Severity: 3

Description

stdout.log
sanityn test_77e: @@@@@@ FAIL: failed to set TBF policy
Trace dump:
= /usr/lib64/lustre/tests/../tests/test-framework.sh:4676:error()
= /usr/lib64/lustre/tests/sanityn.sh:3042:test_77e()
= /usr/lib64/lustre/tests/../tests/test-framework.sh:4936:run_one()
= /usr/lib64/lustre/tests/../tests/test-framework.sh:4972:run_one_logged()
= /usr/lib64/lustre/tests/../tests/test-framework.sh:4778:run_test()
= /usr/lib64/lustre/tests/sanityn.sh:3077:main()
Dumping lctl log to /tmp/test_logs/1478917485/sanityn.test_77e.*.1478917491.log
fre0308: Warning: Permanently added 'fre0307,192.168.103.7' (RSA) to the list of known hosts.
fre0306: Warning: Permanently added 'fre0307,192.168.103.7' (RSA) to the list of known hosts.
fre0305: Warning: Permanently added 'fre0307,192.168.103.7' (RSA) to the list of known hosts.
Resetting fail_loc and fail_val on all nodes...done.
FAIL 77e (2s)
cleanup: ======================================================
== sanityn test complete, duration 7 sec == 02:24:52 (1478917492)
sanityn: FAIL: test_77e failed to set TBF policy
Stopping clients: fre0307,fre0308 /mnt/lustre2 (opts
Stopping client fre0308 /mnt/lustre2 opts:

stderr.log
fre0305: error: set_param: setting /proc/sys/lnet/debug=-lfsck: Invalid argument
pdsh@fre0307: fre0305: ssh exited with exit code 1
fre0306: error: set_param: setting /proc/sys/lnet/debug=-lfsck: Invalid argument
pdsh@fre0307: fre0306: ssh exited with exit code 1
fre0305: error: set_param: /proc/{fs,sys}/{lnet,lustre}/osd-ldiskfs/track_declares_assert: Found no match
fre0306: error: set_param: /proc/{fs,sys}/{lnet,lustre}/osd-ldiskfs/track_declares_assert: Found no match
1 0 records in
1 0 records out
1048576 bytes (1.0 MB) copied, 0.121652 s, 8.6 MB/s
running as uid/gid/euid/egid 500/500/500/500, groups:
[touch] [/mnt/lustre/d0_runas_test/f27046]

Comments

[Gerrit Updater]

jadhav.vikram ([e-mail]) uploaded a new patch: https://review.whamcloud.com/27660
Subject: LU-9669 tests: check required nrs availability on a facet
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 71c2b40291fa9e3b78d9a5df71e782ad8677d71f

[Andreas Dilger]

What versions are involved here?  Typically the tests will run with the version used by the client, and many of the tests already have version-based exclusions for older servers.

 

It would be better to add version-based checks as is done with many other tests, rather than functionality-based checks, since there is a chance that a bug is introduced that returns an error when setting the NRS policy (e.g. conversion from procfs to sysfs) that will result in the tests being "skipped" when they should have actually failed.

[Elena Gryaznova]

Hello Andreas.
Sometimes we have to avoid the version-based checks because of Lustre versions on our servers (Seagate, Cray) does not totally match to osfs Lustre versions.
Example: NEO3.x servers are still 2.7.22, and test_77[e,f] will be skipped because of version based check :

test_77e() {
        local server_version=$(lustre_version_code ost1)
        [[ $server_version -ge $(version_code 2.7.58) ]] ||
                { skip "Need server version newer than 2.7.57"; return 0; }

The same for our 2.5 Lustre based servers.

Thanks.

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/27660/
Subject: LU-9669 tests: check required nrs availability on a facet
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 9d6285695745b0a1289a2827d112bd18a687ab34

[Peter Jones]

Landed for 2.11