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

sanity-lnet test_304: Unexpected peer configuration

XMLWordPrintable

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

      This issue was created by maloo for Marc Vef <mvef@whamcloud.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/e7d104d8-0002-46b1-800d-616bba999046

      test_304 failed with the following error:

      Unexpected peer configuration
      

      Test session details:
      clients: https://build.whamcloud.com/job/lustre-reviews/113564 - 5.14.21-150500.55.73-default
      servers: https://build.whamcloud.com/job/lustre-reviews/113564 - 4.18.0-553.46.1.el8_lustre.x86_64

      10.240.16.0/20 dev eth0 proto kernel scope link src 10.240.25.192
      NI 10.240.25.192@tcp expect status "up" found "up"
      NI 10.1.2.3@tcp expect status "up" found "up"
      /usr/sbin/lnetctl peer add --prim_nid 10.1.2.3@tcp --lock_prim
      /usr/sbin/lnetctl peer set --nid 10.1.2.3@tcp --state 1048577
      /usr/sbin/lnetctl discover 10.240.25.192@tcp
      discover:
      - primary nid: 10.1.2.3@tcp
        Multi-Rail: true
        peer_ni:
        - nid: 10.240.25.192@tcp
        - nid: 10.1.2.3@tcp
      Expected:
      peer:
          - primary nid: 10.1.2.3@tcp
            Multi-Rail: True
            peer ni:
              - nid: 10.240.25.192@tcp
                state: NA
              - nid: 10.1.2.3@tcp
                state: NA
      Actual:
      peer:
      -     primary nid: 10.240.25.196@tcp
            Multi-Rail: false
            peer ni:
            -     nid: 10.240.25.196@tcp
                  state: NA
      -     primary nid: 10.1.2.3@tcp
            Multi-Rail: true
            peer ni:
            -     nid: 10.240.25.192@tcp
                  state: NA
            -     nid: 10.1.2.3@tcp
                  state: NA
       sanity-lnet test_304: @@@@@@ FAIL: Unexpected peer configuration 
        Trace dump:
        = /usr/lib64/lustre/tests/test-framework.sh:7249:error()
        = /usr/lib64/lustre/tests/sanity-lnet.sh:4400:test_304()
        = /usr/lib64/lustre/tests/test-framework.sh:7622:run_one()
        = /usr/lib64/lustre/tests/test-framework.sh:7685:run_one_logged()
        = /usr/lib64/lustre/tests/test-framework.sh:7503:run_test()
        = /usr/lib64/lustre/tests/sanity-lnet.sh:4411:main()
      Dumping lctl log to /autotest/autotest-1/2025-05-22/lustre-reviews_review-ldiskfs_113564_53_e5ff90f3-dc4a-49a2-9752-49ac311f2556//sanity-lnet.test_304.*.1747927984.log
      CMD: onyx-140vm1,onyx-140vm14,onyx-140vm2,onyx-140vm3 /usr/sbin/lctl dk > /autotest/autotest-1/2025-05-22/lustre-reviews_review-ldiskfs_113564_53_e5ff90f3-dc4a-49a2-9752-49ac311f2556//sanity-lnet.test_304.debug_log.\$(hostname -s).1747927984.log;
      		dmesg > /autotest/autotest-1/2025-05-22/lustre-reviews_review-ldiskfs_113564_53_e5ff90f3-dc4a-49a2-9752-49ac311f2556//sanity-lnet.test_304.dmesg.\$(hostname -s).1747927984.log
      onyx-140vm2: invalid parameter 'dump_kernel'
      onyx-140vm2: open(dump_kernel) failed: No such file or directory
      onyx-140vm3: invalid parameter 'dump_kernel'
      onyx-140vm3: open(dump_kernel) failed: No such file or directory
      

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity-lnet test_304 - Unexpected peer configuration

            wc-triage WC Triage
            maloo Maloo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: