[LU-15411] sanity test_272a always fails on single OST system, should be skipped

• Status: Open
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Spencer Burris
• Assignee: WC Triage
• Resolution: Unresolved
• Labels: tests

Environment

• Lustre 2.14
• 4.19.0-21-amd64 #1 SMP Debian 4.19.208-3 (2017-12-06) x86_64 GNU/Linux

• Epic/Theme: test
• Severity: 1

Description

Sanity test_272a always fails on single OST systems because it checks for a stripe count of two, requiring >1 OST.

results.yml:

            name: test_272a
            status: FAIL
            duration: 1
            return_code: 1
            error: "bad\ final\ stripe\ count:\ 1\ \!=\ 2"

test log:

== sanity test 272a: DoM migration: new layout with the same DOM component =========================== 15:28:11 (1641338891)
1+0 records in
1+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.00540308 s, 97.0 MB/s
 sanity test_272a: @@@@@@ FAIL: bad final stripe count: 1 != 2
  Trace dump:
  = /usr/lib/lustre/tests/test-framework.sh:6273:error()
  = /usr/lib/lustre/tests/sanity.sh:20792:test_272a()
  = /usr/lib/lustre/tests/test-framework.sh:6576:run_one()
  = /usr/lib/lustre/tests/test-framework.sh:6623:run_one_logged()
  = /usr/lib/lustre/tests/test-framework.sh:6465:run_test()
  = /usr/lib/lustre/tests/sanity.sh:20794:main()
Dumping lctl log to /opt/results//2022-01-04/134313/sanity.test_272a.*.1641338891.log
Dumping logs only on local client.
Resetting fail_loc on all nodes...done.

 
This test should be skipped as others are on configurations with a single OST. For example:

        (( $OSTCOUNT >= 2 )) || skip_env "needs >= 2 OSTs"

as can be seen in ost-pools.sh.

Comments

[Patrick Farrell]

Spencer,

Just a warning/thought:
If you're testing on a single OST system, you may see a lot of failures in testing, either constantly or rarer random failures, from issues in the test framework.

That's because while there is some attempt to check for a minimum of OSTs in some cases, the test framework defaults to two OSTs, and since a single OST is not a configuration that is expected for a real deployment, it doesn't get much (if any) testing.

This is all to say that I think testing with a single OST may make for a lot of work for not much benefit.  Just something to consider if you're thinking about where to spend testing time.