[LU-4168] Interop 2.4.1<->2.5 failure on test suite conf-sanity test_75 Created: 28/Oct/13  Updated: 22/Dec/17  Resolved: 22/Dec/17

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

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

server: 2.4.1 RHEL6 ldiskfs
client lustre-b2_5 build #2 RHEL6 ldiskfs


Severity: 3
Rank (Obsolete): 11297

 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/75f79ad4-3eb9-11e3-a21b-52540035b04c.

The sub-test test_75 failed with the following error:

add mds1 failed for new params

test log

CMD: client-32vm3 mkfs.lustre --mgs --fsname=lustre --index=0 --mdt --param=sys.timeout=20 --param=lov.stripesize=1048576 --param=lov.stripecount=0 --param=mdt.identity_upcall=/usr/sbin/l_getidentity --backfstype=ldiskfs --device-size=2097152 --mkfsoptions=\"-E lazy_itable_init\" --reformat /dev/lvm-MDS/P1
client-32vm3: mkfs.lustre: '--index' only valid for MDT,OST


 Comments   
Comment by Oleg Drokin [ 29/Oct/13 ]

This is one of those tests that needs to be amended to not run on older server versions where the code is still buggy.

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:40:16 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.