[LU-4662] Test failure on test suite sanity, subtest test_228a Created: 23/Feb/14  Updated: 04/Mar/14  Resolved: 04/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0, Lustre 2.5.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 12762

 Description   

This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/791d1644-9be8-11e3-9b49-52540035b04c.

The sub-test test_228a failed with the following error:

old blk1=952, new blk2=, unmatched!

Info required for matching: sanity 228a

 Comments   
Comment by Jian Yu [ 24/Feb/14 ]

The same failure occurred on master branch while verifying patch http://review.whamcloud.com/8918 :
https://maloo.whamcloud.com/test_sets/df426b18-9bc5-11e3-91dc-52540035b04c

Comment by Oleg Drokin [ 26/Feb/14 ]

Looks like some sort of test system issue to me:

CMD: shadow-9vm12 debugfs -c -R \"stat oi.16.28\" /dev/lvm-Role_MDS/P1
pdsh@shadow-9vm5: gethostbyname("shadow-9vm12") failed
/usr/lib64/lustre/tests/sanity.sh: line 11519: [: 952: unary operator expected
 sanity test_228a: @@@@@@ FAIL: old blk1=952, new blk2=, unmatched!

so name resolution somehow broke?

Comment by Jian Yu [ 04/Mar/14 ]

Seems so, Oleg.
By searching on Maloo, I found that the test 228a and 228c failure in this ticket each only occurred one time. So, let's close this ticket. If the failure occurred again, I'll reopen this ticket.

Generated at Sat Feb 10 01:44:45 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.