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

change test-framework to detect active facet based on current Lustre state

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Lustre 2.7.0
    • 3
    • 9223372036854775807

    Description

      Lustre failover tests can not be ran test-by-test (ONLY=1 replay-dual.sh && ONLY=2 replay-dual.sh) on the setup with ${facet}_HOST != ${facet}failover_HOST.
      t-f keeps the "active" facet info in "${facet}active" files, which are created
      when facet_failover() is executed first time in the test session.
      Before facet_failover() executed these files are empty and
      active facet is ${facet} by default.
      In case when tests are executed test-by-test the active facet is
      ${facet}failover after 1st test completed, and 2nd test is started
      having ${facet}failover active without this info stored in
      ${facet}active files.

      It looks reasonable to detect active facet based on current state.

      Attachments

        Issue Links

          Activity

            People

              egryaznova Elena Gryaznova
              egryaznova Elena Gryaznova
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: