[LU-7151] sanity test_205:No jobstats for id.205.dd.3 found

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.9.0
• Severity: 3
• Assignee: Yang Sheng
• Reporter: Maloo

Description

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

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/3c102cfc-5a21-11e5-9147-5254006e85c2.

The sub-test test_205 failed with the following error:

No jobstats for id.205.dd.3 found on ost1::*.lustre-OST0000.job_stats

sanity test_205: @@@@@@ FAIL: No jobstats for id.205.dd.3 found on ost1::*.lustre-OST0000.job_stats 
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:4748:error_noexit()
  = /usr/lib64/lustre/tests/test-framework.sh:4779:error()
  = /usr/lib64/lustre/tests/sanity.sh:11566:verify_jobstats()
  = /usr/lib64/lustre/tests/sanity.sh:11641:test_205()
  = /usr/lib64/lustre/tests/test-framework.sh:5026:run_one()
  = /usr/lib64/lustre/tests/test-framework.sh:5063:run_one_logged()
  = /usr/lib64/lustre/tests/test-framework.sh:4928:run_test()
  = /usr/lib64/lustre/tests/sanity.sh:11676:main()
Dumping lctl log to /logdir/test_logs/2015-09-13/lustre-reviews-el6_7-x86_64--review-zfs-part-1--1_8_1__34549__-69995635271220-045433/sanity.test_205.*.1442125355.log
CMD: shadow-22vm12,shadow-22vm2,shadow-22vm3,shadow-22vm5.shadow.whamcloud.com /usr/sbin/lctl dk > /logdir/test_logs/2015-09-13/lustre-reviews-el6_7-x86_64--review-zfs-part-1--1_8_1__34549__-69995635271220-045433/sanity.test_205.debug_log.\$(hostname -s).1442125355.log;

Issue Links

• is related to: LU-6920 sanity test_205 failed with old jobstats not expired

Comments

[James Nunez (Inactive)]

Another failure on master:
2015-12-30 10:12:17 - https://testing.hpdd.intel.com/test_sets/335705ae-af3a-11e5-8114-5254006e85c2
2016-01-04 20:26:29 - https://testing.hpdd.intel.com/test_sets/a73a93c8-b368-11e5-bf32-5254006e85c2

[Bob Glossman (Inactive)]

another on master/sles12:
https://testing.hpdd.intel.com/test_sets/495bbe8e-ade7-11e5-bf32-5254006e85c2

this happens enough with sles12 client on master that I'm starting to think it may be a 100% fail with that combination.

[Bob Glossman (Inactive)]

another master/sles12:
https://testing.hpdd.intel.com/test_sets/cca376fc-a954-11e5-a735-5254006e85c2

[Bob Glossman (Inactive)]

another on master, sles12 client;
https://testing.hpdd.intel.com/test_sets/8ca730b4-9f92-11e5-a7bd-5254006e85c2

[Bob Glossman (Inactive)]

another on master with sles12 client:
https://testing.hpdd.intel.com/test_sets/1161a6b0-a05e-11e5-a33d-5254006e85c2

[Sarah Liu]

similar issue on SELinux enabled client after upgrade from 2.5.5 to master

https://testing.hpdd.intel.com/test_sets/6b88b5b0-8f0c-11e5-8dd0-5254006e85c2

[Bob Glossman (Inactive)]

another on master:
https://testing.hpdd.intel.com/test_sets/f84f189e-891d-11e5-9de3-5254006e85c2

[James Nunez (Inactive)]

Another failure at https://testing.hpdd.intel.com/test_sets/36edfaea-7e13-11e5-88df-5254006e85c2