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

sanity-hsm test 70, 71 and 72 fails with "Failed to start copytool monitor "

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.6.0, Lustre 2.5.1
    • Lustre 2.5.1
    • RHEL 6.5 Lustre 2.5.1 RC3 OpenSFS cluster with single MGS/MDS, single OSS with two OSTs, one node running Robinhood, one agent/client and one client
    • 3
    • 13079

    Description

      Test suite sanity-hsm tests 70, 71 and 72 all fail with 

      Failed to start copytool monitor on c19

      Test logs are at https://maloo.whamcloud.com/test_sets/7f2aafdc-a959-11e3-95fe-52540035b04c

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-4020 HSM copytool event monitoring capabilities

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

          Activity

            [LU-4751] sanity-hsm test 70, 71 and 72 fails with "Failed to start copytool monitor "
            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
            jamesanunez James Nunez (Inactive) added a comment -

            Mike,

            Your patch works with -Rssh and gets me past the copytool start up.

            Thanks.

            jamesanunez James Nunez (Inactive) added a comment - Mike, Your patch works with -Rssh and gets me past the copytool start up. Thanks.
            mjmac Michael MacDonald (Inactive) added a comment -

            Sigh. In dealing with the nuances of running backgrounded processes via mrsh, I inadvertently introduced a hard dependency on it. Environments with -Rssh (or, indeed, any valid non-mrsh $PDSH) shouldn't be using the workaround.

            The following fix has been validated to work with -Rmrsh: http://review.whamcloud.com/9587

            James, please confirm when possible that the fix also works with -Rssh.

            mjmac Michael MacDonald (Inactive) added a comment - Sigh. In dealing with the nuances of running backgrounded processes via mrsh, I inadvertently introduced a hard dependency on it. Environments with -Rssh (or, indeed, any valid non-mrsh $PDSH) shouldn't be using the workaround. The following fix has been validated to work with -Rmrsh: http://review.whamcloud.com/9587 James, please confirm when possible that the fix also works with -Rssh.
            pjones Peter Jones added a comment -

            Mike is looking into this

            pjones Peter Jones added a comment - Mike is looking into this

            People

              mjmac Michael MacDonald (Inactive)
              jamesanunez James Nunez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: