Details

    • Technical task
    • Resolution: Fixed
    • Major
    • Lustre 2.7.0
    • Lustre 2.5.0
    • 10416

    Description

      This issue was created by maloo for John Hammond <john.hammond@intel.com>

      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

      Attachments

        Issue Links

          Activity

            [LU-3939] Test failure on test suite sanity-hsm, subtest test_40
            utopiabound Nathaniel Clark added a comment - This issue is still occurring on master: review-zfs: https://maloo.whamcloud.com/test_sets/0aa1078c-e2f3-11e3-8561-52540035b04c https://maloo.whamcloud.com/test_sets/47ce19b2-dff4-11e3-9854-52540035b04c https://maloo.whamcloud.com/test_sets/75f2680a-c5f7-11e3-a760-52540035b04c full (ldiskfs): https://maloo.whamcloud.com/test_sets/6637dbbc-aa80-11e3-bd80-52540035b04c https://maloo.whamcloud.com/test_sets/be4e5838-a5e1-11e3-aac5-52540035b04c
            pjones Peter Jones added a comment -

            Fixed for 2.5.1 and 2.6. Similar fixes for other tests can be tracked under a separate ticket.

            pjones Peter Jones added a comment - Fixed for 2.5.1 and 2.6. Similar fixes for other tests can be tracked under a separate ticket.

            Bob this failure, even if it looks of the same kind of problem, is against test_90 not test_40.
            BTW, it is a good point for John's remark that others tests that do not require a shared storage should use the same fix I applied for test_40.

            bfaccini Bruno Faccini (Inactive) added a comment - Bob this failure, even if it looks of the same kind of problem, is against test_90 not test_40. BTW, it is a good point for John's remark that others tests that do not require a shared storage should use the same fix I applied for test_40.
            bogl Bob Glossman (Inactive) added a comment - seen in master: https://maloo.whamcloud.com/test_sessions/bcd51864-9459-11e3-b8a9-52540035b04c
            yujian Jian Yu added a comment - 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

            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.

            jhammond John Hammond added a comment - 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.

            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.

            bfaccini Bruno Faccini (Inactive) added a comment - 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.

            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.

            bfaccini Bruno Faccini (Inactive) added a comment - 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.

            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 ??

            bfaccini Bruno Faccini (Inactive) added a comment - 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 ??

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

            bfaccini Bruno Faccini (Inactive) added a comment - Submitted definitive version/patch-set #6 of http://review.whamcloud.com/7703 , which additionally re-enable test_40.

            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.

            bfaccini Bruno Faccini (Inactive) added a comment - 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.

            People

              bfaccini Bruno Faccini (Inactive)
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: