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

conf-sanity test_32b: FAIL: list verification failed and test_32b failed with 4

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.10.0
    • Lustre 2.8.0
    • 1 Client, 1 MDT, 2 OST (master)
    • 3
    • 9223372036854775807

    Description

      conf-sanity test_32b failed for SElinux enabled client with the following error:

      conf-sanity test_32b: @@@@@@ FAIL: list verification failed 
        Trace dump:
        = /usr/lib64/lustre/tests/test-framework.sh:4812:error_noexit()
        = /usr/lib64/lustre/tests/conf-sanity.sh:2069:t32_test()
        = /usr/lib64/lustre/tests/conf-sanity.sh:2203:test_32b()
        = /usr/lib64/lustre/tests/test-framework.sh:5090:run_one()
        = /usr/lib64/lustre/tests/test-framework.sh:5127:run_one_logged()
        = /usr/lib64/lustre/tests/test-framework.sh:4992:run_test()
        = /usr/lib64/lustre/tests/conf-sanity.sh:2207:main()
      Dumping lctl log to /tmp/test_logs/2015-11-23/162346/conf-sanity.test_32b.*.1448327619.log
      eagle-52vm5: Host key verification failed.
      eagle-52vm5: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm5: rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
      eagle-52vm3: Host key verification failed.
      eagle-52vm3: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm3: rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
      eagle-52vm2: Host key verification failed.
      eagle-52vm2: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
      eagle-52vm2: rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
       conf-sanity test_32b: @@@@@@ FAIL: test_32b failed with 4 
      
      

      Attachments

        Issue Links

          Activity

            [LU-7497] conf-sanity test_32b: FAIL: list verification failed and test_32b failed with 4

            there could be other test failure with conf-sanity:32 - so let's reopen it after more is seen

            jay Jinshan Xiong (Inactive) added a comment - there could be other test failure with conf-sanity:32 - so let's reopen it after more is seen
            pjones Peter Jones added a comment -

            Landed for 2.10

            pjones Peter Jones added a comment - Landed for 2.10

            Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/25940/
            Subject: LU-7497 tests: Fix test failure in conf-sanity 32b
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: c9f12540412a429b824dbc83c1c8b00c8affe28a

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/25940/ Subject: LU-7497 tests: Fix test failure in conf-sanity 32b Project: fs/lustre-release Branch: master Current Patch Set: Commit: c9f12540412a429b824dbc83c1c8b00c8affe28a

            Jinshan Xiong (jinshan.xiong@intel.com) uploaded a new patch: https://review.whamcloud.com/25940
            Subject: LU-7497 tests: Fix test failure in conf-sanity 32b
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 831542123aaa9bafe48e0d5adcc7b89857570993

            gerrit Gerrit Updater added a comment - Jinshan Xiong (jinshan.xiong@intel.com) uploaded a new patch: https://review.whamcloud.com/25940 Subject: LU-7497 tests: Fix test failure in conf-sanity 32b Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 831542123aaa9bafe48e0d5adcc7b89857570993
            jay Jinshan Xiong (Inactive) added a comment - - edited

            it turned out that the tarball 'disk2_4-zfs.tar.bz2' has mgs enabled for OST device so the starting of ost failed because MGS has already been started along with the MDT.

            I'm talking about the test failure with error message 'test_32b failed with 1'

            jay Jinshan Xiong (Inactive) added a comment - - edited it turned out that the tarball 'disk2_4-zfs.tar.bz2' has mgs enabled for OST device so the starting of ost failed because MGS has already been started along with the MDT. I'm talking about the test failure with error message 'test_32b failed with 1'
            adilger Andreas Dilger added a comment - +1 for ZFS https://testing.hpdd.intel.com/test_sets/2cb46a64-ff72-11e6-9df3-5254006e85c2

            People

              niu Niu Yawei (Inactive)
              standan Saurabh Tandan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: