[LU-3921] Interop 2.4.0<->2.5 failure on test suite sanity test_160: current index should be 14 is 0 Created: 11/Sep/13  Updated: 22/Dec/17  Resolved: 22/Dec/17

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

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

Severity: 3
Rank (Obsolete): 10359

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/f5eae562-19c4-11e3-bb73-52540035b04c.

The sub-test test_160 failed with the following error:

current index should be 14 is 0

CMD: client-32vm3 /usr/sbin/lctl get_param -n mdd.lustre-MDT0000.changelog_users
verifying index survives MDT restart: 14 == 0
 sanity test_160: @@@@@@ FAIL: current index should be 14 is 0 


 Comments   
Comment by Oleg Drokin [ 13/Sep/13 ]

another test taht needs to make sure the version on the server knows how to do the right thing

Comment by Andreas Dilger [ 22/Dec/17 ]

Close old bug that has not been seen in a long time.

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