[LU-3939] Test failure on test suite sanity-hsm, subtest test_40

• Type: Technical task
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.7.0
• Affects Version/s: Lustre 2.5.0
• Labels: HSM
• Assignee: Bruno Faccini (Inactive)
• Reporter: Maloo

Description

This issue was created by maloo for John Hammond <[e-mail]>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/b8769b2e-1b6b-11e3-a00a-52540035b04c.

The sub-test test_40 failed with the following error:

requests did not complete

Info required for matching: sanity-hsm 40

Issue Links

• is related to: LU-5474 Test failure sanity-hsm test_90: requests did not complete
• is related to: LU-4126 sanity-hsm test_15 failure: 'requests did not complete'

Comments

[Bob Glossman (Inactive)]

seen in master:
https://maloo.whamcloud.com/test_sessions/bcd51864-9459-11e3-b8a9-52540035b04c

[Jian Yu]

While validating patches for Lustre b2_5 branch, this failure occurred frequently:
https://maloo.whamcloud.com/test_sets/631324a2-76bc-11e3-9ce8-52540035b04c
https://maloo.whamcloud.com/test_sets/a365b8f0-7737-11e3-9ce8-52540035b04c

Back-port patch http://review.whamcloud.com/7703/ to Lustre b2_5 branch: http://review.whamcloud.com/8771

[John Hammond]

Hi Bruno, I have a suggestion here. Can we determine which tests actually require that the HSM archive be on shared storage? I was thinking that perhaps only those tests should use shared storage and the other (normal) tests should use local /tmp on the copytool client. Based on a sanity-hsm run on 4 of my own VMs it seems that most tests are fine with a local HSM archive.

[Bruno Faccini (Inactive)]

BTW, new auto-test session Change #7703/patch-set #6, now show successful run of test_40 with a local/tmp hsm-root/HSM_ARCHIVE.

[Bruno Faccini (Inactive)]

Now that TEI-1041 has definitely reverted ALL auto-tests settings causing sanity-hsm/test_40 sub-test to be disabled, I have re-triggered build (can not only re-trigger auto-tests since build has been removed during interval) of Change #7703/patch-set #6.

[Bruno Faccini (Inactive)]

Humm, even with my change line to re-enable test_40 in patch-set #6, auto-tests report still show it as "skipping excluded test 40" … Could it be that TEI-570 setting was not reverted by TEI-1041 as expected ??

[Bruno Faccini (Inactive)]

Submitted definitive version/patch-set #6 of http://review.whamcloud.com/7703, which additionally re-enable test_40.

[Bruno Faccini (Inactive)]

Since change #7374 for LU-3815, excluding test_40 sub-test in sanity-hsm, has land since about 10 days now, it sounds reasonable to ask Tools-team to revert their changes in TEI-570. So I re-open TEI-570.

[Bruno Faccini (Inactive)]

Jinshan just added test_40 to sanity-hsm exclusion-list in his change http://review.whamcloud.com/7374 for LU-3815, so I will abandon http://review.whamcloud.com/7772.

Need to wait now for Jinshan's patch to land (+ a few days to wait everybody time to rebase !!) in order to ask Tools-team to revert their changes in TEI-570.

[Bruno Faccini (Inactive)]

Submitted patch-set #4 of http://review.whamcloud.com/7703, including a hack to avoid TEI-570 changes effect and thus allow my changes to sanity-hsm/test_40 to be exposed in auto-tests environment.

On the other hand I am trying to get test_40 be included in sanity-hsm sub-tests exception list, by the mean of http://review.whamcloud.com/7772 or better within Jinshan's change http://review.whamcloud.com/7374 for LU-3815, in order to be able to ask Tools-team for TEI-570 changes to be reverted.

[Bruno Faccini (Inactive)]

http://review.whamcloud.com/7772 just submitted to insert sanity-hsm/test_40 in ALWAYS_EXCEPT list.

When landed, it will allow us to ask the Tools team to revert their changes in TEI-570, and then to remove it on-demand from exception list ...

On the other hand, I am waiting from current auto-tests results of http://review.whamcloud.com/7703, to address comments and any other issues before to push a new+definitive patch-set.