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

create conf-sanity.sh test_32 ZFS upgrade test image

Details

    • 3
    • 6276

    Description

      In order to ensure that we do not break ZFS upgrades in the future, a filesystem test image is needed for conf-sanity.sh test_32a.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. LU-4406 conf-sanity test_32a: Upgrade from b2_4-zfs to master failed

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-4543 Failure on test suite conf-sanity test_32b: list verification failed

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. LU-4074 Failure on test suite conf-sanity test_32b

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-3349 Add b2_3/b2_4 ldisk image tarball for conf-sanity.sh test_32

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            [LU-2687] create conf-sanity.sh test_32 ZFS upgrade test image
            pjones Peter Jones added a comment -

            Landed for 2.5.1 and 2.6

            pjones Peter Jones added a comment - Landed for 2.5.1 and 2.6
            sarah Sarah Liu added a comment - - edited

            http://review.whamcloud.com/#/c/7193/

            sarah Sarah Liu added a comment - - edited http://review.whamcloud.com/#/c/7193/
            sarah Sarah Liu added a comment -

            I will work on this. I've create b2_3 image, but not for zfs.

            sarah Sarah Liu added a comment - I will work on this. I've create b2_3 image, but not for zfs.
            emoly.liu Emoly Liu added a comment -

            Maybe Sarah is working on this. Is there anything I can help with?

            emoly.liu Emoly Liu added a comment - Maybe Sarah is working on this. Is there anything I can help with?
            adilger Andreas Dilger added a comment -

            Emoly, Sarah, I think one of you were working on this already? Is this a duplicate bug with another one where you are doing your work?

            adilger Andreas Dilger added a comment - Emoly, Sarah, I think one of you were working on this already? Is this a duplicate bug with another one where you are doing your work?
            adilger Andreas Dilger added a comment -

            Correct - we only want a single image per release tag. However, since LLNL is already running in production with the current development tag, it would be good to create the disk2_4-zfs.tar.bz2 test image in advance of the release to ensure that we don't break anything in the run-up to the final 2.4.0 release. If there is a well-understood reason to break compatibility with the development code, we can always create a new image, but if we accidentally break compatibility and don't know about it that would is a problem we could avoid.

            adilger Andreas Dilger added a comment - Correct - we only want a single image per release tag. However, since LLNL is already running in production with the current development tag, it would be good to create the disk2_4-zfs.tar.bz2 test image in advance of the release to ensure that we don't break anything in the run-up to the final 2.4.0 release. If there is a well-understood reason to break compatibility with the development code, we can always create a new image, but if we accidentally break compatibility and don't know about it that would is a problem we could avoid.
            liwei Li Wei (Inactive) added a comment -

            My understanding is that images should be created with releases (e.g., 2.1.1, 2.4.0, etc.) but not development tags (e.g., 2.3.59, 2.4.0-rc3). Having too many images checked in would grow the size of the Git repository and, if I understand correctly, they would be difficult to get ride of, given the version control nature. Hence, I think Andreas wants a ZFS image from the final 2.4.0 release tag, unless he explicitly requests otherwise.

            liwei Li Wei (Inactive) added a comment - My understanding is that images should be created with releases (e.g., 2.1.1, 2.4.0, etc.) but not development tags (e.g., 2.3.59, 2.4.0-rc3). Having too many images checked in would grow the size of the Git repository and, if I understand correctly, they would be difficult to get ride of, given the version control nature. Hence, I think Andreas wants a ZFS image from the final 2.4.0 release tag, unless he explicitly requests otherwise.
            adilger Andreas Dilger added a comment -

            Adding Li Wei, since he wrote the original test_32newtarball() script.

            adilger Andreas Dilger added a comment - Adding Li Wei, since he wrote the original test_32newtarball() script.

            People

              sarah Sarah Liu
              adilger Andreas Dilger
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: