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

use $LST path in lst.sh and sanity-lnet

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • None
    • 3
    • 9223372036854775807

      lst.sh invoked the 'lst' binary by bare name, so it only worked when
      lst was installed in the PATH. When running from a build tree lst is
      built in lnet/utils/ and is not installed, so sanity-lnet tests 220,
      228 and 257 failed instead of running (or skipping cleanly).

      Resolve the lst binary in lst.sh: honour an $LST full pathname if one
      is given, otherwise look for $LUSTRE/../lnet/utils/lst, and finally
      fall back to the PATH. All lst invocations now use $LST, and the
      "cannot find lst" error reports the pathname that was tried.

      In test-framework.sh add $LUSTRE/../lnet/utils to the PATH alongside
      the other build-tree utility directories, and silence the stderr of
      the 'which lst' fallback when lst is not installed.

      In sanity-lnet.sh add check_lst_tools() so tests that need lst.sh and
      lst skip with a clear message when those tools are unavailable, rather
      than failing.

      Also replace the load_modules() call in cleanup_testsuite() with a new
      restore_lnet() helper that reloads only the LNet modules that
      cleanup_lnet() unloaded. This suite never needs the server stack, and
      load_modules() additionally pulls in the OSD modules, which can fail
      on nodes where their dependencies are not loadable - e.g. osd_zfs
      needs ZFS modules that are not installed for the running kernel.

            wc-triage WC Triage
            shadow Alexey Lyashkov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: