Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-4349

conf-sanity test_47: test failed to respond and timed out

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • Lustre 2.6.0, Lustre 2.5.4
    • Lustre 2.6.0
    • None
    • lustre-master build # 1791 RHEL6 zfs
    • 3
    • 11914

    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/1d5f9fd8-5c6a-11e3-9d08-52540035b04c.

      The sub-test test_47 failed with the following error:

      test failed to respond and timed out

      Info required for matching: conf-sanity 47

      This test took 3600s and failed with timeout, cannot find error logs. I checked
      a PASS conf-sanity run on zfs, the same sub test takes about 134s to complete:

      https://maloo.whamcloud.com/sub_tests/b9351066-5d53-11e3-956b-52540035b04c

      Attachments

        Issue Links

          Activity

            [LU-4349] conf-sanity test_47: test failed to respond and timed out
            pjones Peter Jones added a comment -

            Landed for 2.6

            pjones Peter Jones added a comment - Landed for 2.6

            Minh retriggered the test of Change, 9875 on Shadow today.

            jlevi Jodi Levi (Inactive) added a comment - Minh retriggered the test of Change, 9875 on Shadow today.
            bogl Bob Glossman (Inactive) added a comment - - edited

            We are talking about back port of http://review.whamcloud.com/8997, right? I can do that.

            http://review.whamcloud.com/9875

            bogl Bob Glossman (Inactive) added a comment - - edited We are talking about back port of http://review.whamcloud.com/8997 , right? I can do that. http://review.whamcloud.com/9875
            green Oleg Drokin added a comment -

            Somebody needs to backport the patch from lu-4413 as it could not be cleanly cherry-picked to b2_5

            green Oleg Drokin added a comment - Somebody needs to backport the patch from lu-4413 as it could not be cleanly cherry-picked to b2_5
            sarah Sarah Liu added a comment -

            Hi Jodi,
            No, I didn't see this issue in tag-2.5.57 testing

            sarah Sarah Liu added a comment - Hi Jodi, No, I didn't see this issue in tag-2.5.57 testing

            Sarah,
            Did you hit this on the 2.5.57 tag testing?

            jlevi Jodi Levi (Inactive) added a comment - Sarah, Did you hit this on the 2.5.57 tag testing?

            set ticket as replated to LU-4413 just because of the similar symptoms

            tappro Mikhail Pershin added a comment - set ticket as replated to LU-4413 just because of the similar symptoms

            Last two issues were happened in branches without LU-4413 fix mentioned in Fan Yong comment. We have to port http://review.whamcloud.com/8997 to the b2_5 it seems

            tappro Mikhail Pershin added a comment - Last two issues were happened in branches without LU-4413 fix mentioned in Fan Yong comment. We have to port http://review.whamcloud.com/8997 to the b2_5 it seems
            bogl Bob Glossman (Inactive) added a comment - may be the same issue, seen in b2_5: https://maloo.whamcloud.com/test_sets/550c0fde-a521-11e3-9fee-52540035b04c
            sarah Sarah Liu added a comment -

            Hit this issue again during tag-2.5.56 testing in DNE mode

            https://maloo.whamcloud.com/test_sets/92cc87f8-a02c-11e3-947c-52540035b04c

            sarah Sarah Liu added a comment - Hit this issue again during tag-2.5.56 testing in DNE mode https://maloo.whamcloud.com/test_sets/92cc87f8-a02c-11e3-947c-52540035b04c

            People

              tappro Mikhail Pershin
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: