[LU-3449] Interop failure on many testsuites: error: set_param: track_declares_assert: Found no match

Related — Thu, 15 Aug 2013 06:36:16 +0000

Several test suites fail during Interop testing due to a call to lctl set_param to set osd-ldiskfs.track_declares_assert=1. From test-framework.sh

if [ -n "$OSD_TRACK_DECLARES_LBUG" ] ; then
  do_nodes $(comma_list $(mdts_nodes) $(osts_nodes)) \
  "$LCTL set_param osd-*.track_declares_assert=1" \
    > /dev/null
fi

Setting track_declares_assert was added in 2.3.65.

Two Interop test runs have failed with these errors:
June 8, b2_3 servers, master clients: https://maloo.whamcloud.com/test_sessions/aaa56180-d08c-11e2-a7e3-52540035b04c

June 7, b2_3 servers, b2_4 clients: replay-vbr maybe more: https://maloo.whamcloud.com/test_sessions/f0211dda-cf83-11e2-a604-52540035b04c

I have also run into this error running test locally with b2_1 servers and master clients. So, this is a general problem for interop testing.

From the suite log for the failed test, you see

CMD: client-32vm3 /usr/sbin/lctl get_param -n version
CMD: client-32vm3,client-32vm4,client-32vm5 PATH=/usr/lib64/lustre/tests:/usr/lib/lustre/tests:/usr/lib64/lustre/tests:/opt/iozone/bin:/opt/iozone/bin:/usr/lib64/lustre/tests/mpi:/usr/lib64/lustre/tests/racer:/usr/lib64/lustre/../lustre-iokit/sgpdd-survey:/usr/lib64/lustre/tests:/usr/lib64/lustre/utils/gss:/usr/lib64/lustre/utils:/usr/lib64/openmpi/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin::/sbin:/bin:/usr/sbin: NAME=autotest_config sh rpc.sh set_default_debug \"0x33f0404\" \" 0xffb7e3ff\" 32 
CMD: client-32vm3,client-32vm4 /usr/sbin/lctl set_param 				 osd-ldiskfs.track_declares_assert=1
client-32vm3: error: set_param: /proc/{fs,sys}/{lnet,lustre}/osd-ldiskfs/track_declares_assert: Found no match
client-32vm4: error: set_param: /proc/{fs,sys}/{lnet,lustre}/osd-ldiskfs/track_declares_assert: Found no match

Whamcloud Community JIRA

[LU-3449] Interop failure on many testsuites: error: set_param: track_declares_assert: Found no match