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

UDSP does not import rules of priority 0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Lustre 2.17.0
    • None
    • 9223372036854775807

      `lnetctl udsp add` says it accepts priority values 0 or greater:

      $ lnetctl udsp --help
      udsp add: add a udsp
      [...]
              --priority p:  Assign priority value p where p >= 0.
                             Note: 0 is the highest priority.

      However, rules of priority value zero disappear when restarting lnet, such as after reboot. This is the content of /etc/lnet.conf:

      net:
      -     net type: o2ib
            local NI(s):
            -     interfaces:
                        0: ens11f0np0
                  tunables:
                        peer_timeout: 180
                        peer_credits: 32
                        peer_buffer_credits: 0
                        credits: 1024
                  lnd tunables:
                        peercredits_hiw: 16
                        concurrent_sends: 64
                        map_on_demand: true
                        fmr_pool_size: 2048
                        fmr_flush_trigger: 384
                        fmr_cache: 1
                        ntx: 2048
                        conns_per_peer: 4
                        tos: -1
                  CPT: "[0,1]"
      peer:
      [...]
      global:
          numa_range: 0
          max_interfaces: 200
          discovery: 1
          drop_asym_route: 0
          retry_count: 2
          transaction_timeout: 150
          health_sensitivity: 100
          recovery_interval: 1
          router_sensitivity: 100
          lnd_timeout: 49
          response_tracking: 3
          recovery_limit: 0
          max_recovery_ping_interval: 900
      udsp:
          - idx: 0
            src: o2ib
            action:
                priority: 0
          - idx: 1
            dst: o2ib
            action:
                priority: 0 

      After restarting, lnetctl udsp show returns nothing.

      $ sudo systemctl start lnet
      Job for lnet.service failed because the control process exited with error code.
      See "systemctl status lnet.service" and "journalctl -xeu lnet.service" for details.
      $ sudo journalctl -xeu lnet.service --no-pager
      Sep 02 06:57:04 [hostname] systemd[1]: Starting lnet.service - lnet management...
      ░░ Subject: A start job for unit lnet.service has begun execution
      ░░ Defined-By: systemd
      ░░ Support: http://www.ubuntu.com/support
      ░░
      ░░ A start job for unit lnet.service has begun execution.
      ░░
      ░░ The job identifier is 1434.
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'peercredits_hiw' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'concurrent_sends' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'fmr_pool_size' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'fmr_flush_trigger' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'fmr_cache' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] lnetctl[8844]: Ignoring unrecognized key 'ntx' for 'lnd tunables'
      Sep 02 06:57:04 [hostname] systemd[1]: lnet.service: Main process exited, code=exited, status=234/n/a
      ░░ Subject: Unit process exited
      ░░ Defined-By: systemd
      ░░ Support: http://www.ubuntu.com/support
      ░░
      ░░ An ExecStart= process belonging to unit lnet.service has exited.
      ░░
      ░░ The process' exit code is 'exited' and its exit status is 234.
      Sep 02 06:57:04 [hostname] systemd[1]: lnet.service: Failed with result 'exit-code'.
      ░░ Subject: Unit failed
      ░░ Defined-By: systemd
      ░░ Support: http://www.ubuntu.com/support
      ░░
      ░░ The unit lnet.service has entered the 'failed' state with result 'exit-code'.
      Sep 02 06:57:04 [hostname] systemd[1]: Failed to start lnet.service - lnet management.
      ░░ Subject: A start job for unit lnet.service has failed
      ░░ Defined-By: systemd
      ░░ Support: http://www.ubuntu.com/support
      ░░
      ░░ A start job for unit lnet.service has finished with a failure.
      ░░
      ░░ The job identifier is 1434 and the job result is failed.

      When I modified the priority to 1 instead of 0, the UDSP settings are properly loaded, and can be seen with `lnetctl udsp show`.

       

            wc-triage WC Triage
            seungtaeko Seungtaek O
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: