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

conf-sanity test_30b defect

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.8.0
    • Lustre 2.8.0
    • None
    • 3
    • 9223372036854775807

    Description

      conf-sanity test_30b takes into account only "fake nid" and does not take into account a failover_nid configured for "--failnode".
      This leads test always fails on the setup with ost1failover_HOST != ost1_HOST.
      Example of failure :
      configuration used :

      ost1_HOST=fre812
      ost1failover_HOST=fre811
      

      test fails with :

      Updated after 2s: wanted '192.168.108.32@tcp' got '192.168.108.32@tcp'
      failover_nids: [ 192.168.108.12@tcp, 192.168.108.11@tcp, 192.168.108.32@tcp ]
      should have 2 failover nids: 3
       conf-sanity test_30b: @@@@@@ FAIL: Failover nid not added
      

      NIDCOUNT is equal 2 only if ost1failover_HOST is default (equal to ost1_HOST). In this case failover_nids expected to contain OSTNID and NEW :

      failover_nids: [ <OSTNID>, <NEW> ]
      

      For case ost1failover_HOST != ost1_HOST NIDCOUNT is equal 3 because failover_nids also contains failover_nid configured for failover node (192.168.108.11):

      failover_nids: [ <OSTNID>, <ostfailover nid>, <NEW> ]
      failover_nids: [ 192.168.108.12@tcp, 192.168.108.11@tcp, 192.168.108.32@tcp ]'
      

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: