[LU-12318] conf-sanity test_32b: Timeout occurred after 203 mins

Wed, 22 May 2019 16:55:59 +0000

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

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/636eb924-75ef-11e9-a6f9-52540065bddc

test_32b failed with the following error:

Timeout occurred after 203 mins, last suite running was conf-sanity, restarting cluster to continue tests

From the MDS dmesg

[12014.701596] Lustre: DEBUG MARKER: /usr/sbin/lctl conf_param t32fs-OST0000.failover.node=10.9.6.40@tcp
[12015.001794] Lustre: DEBUG MARKER: /usr/sbin/lctl conf_param t32fs-MDT0000.mdc.max_rpcs_in_flight=9
[12015.300191] Lustre: DEBUG MARKER: /usr/sbin/lctl conf_param t32fs-MDT0000.failover.node=10.9.6.40@tcp
[12015.597066] Lustre: DEBUG MARKER: /usr/sbin/lctl pool_new t32fs.interop
[12016.943730] LustreError: 22754:0:(obd_config.c:1361:class_process_proc_param()) t32fs-OST0000-osc-MDT0000: unknown config parameter 'osc.max_dirty_mb=15'
[12016.947032] Lustre: t32fs-OST0000: Connection restored to 10.9.6.40@tcp (at 0@lo)
[12016.950007] Lustre: t32fs-OST0000: deleting orphan objects from 0x0:394 to 0x0:449
[12017.896930] Lustre: DEBUG MARKER: /usr/sbin/lctl conf_param t32fs-MDT0000.lov.stripesize=4M
[12018.047785] Lustre: Modifying parameter t32fs-MDT0000-mdtlov.lov.stripesize in log t32fs-MDT0000

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
conf-sanity test_32b - Timeout occurred after 203 mins, last suite running was conf-sanity, restarting cluster to continue tests

Whamcloud Community JIRA

[LU-12318] conf-sanity test_32b: Timeout occurred after 203 mins