isis metric not come into effect

[JosiahMg]

Description

I have built a network R1-R2 using Docker FRR10, and the configuration information is as follows.

# R1 
interface eth1
  ip address 10.1.12.1/24
  ip router isis 1

interface eth2
  ip address 10.2.12.1/24
  ip router isis 1

interface eth3
  ip address 10.3.12.1/24
  ip router isis 1

interface lo
  ip address 1.1.1.1/32
  ip router isis 1

router isis 1
  is-type level-1
  net 49.0000.0000.0000.0001.00



# R2
interface eth1
  ip address 10.1.12.2/24
  ip router isis 1
  isis metric 15

interface eth2
  ip address 10.2.12.2/24
  ip router isis 1
  isis metric 5

interface eth3
  ip address 10.3.12.2/24
  ip router isis 1
  isis metric 3

interface lo
  ip address 2.2.2.2/32
  ip router isis 1

router isis 1
  is-type level-1
  net 49.0000.0000.0000.0002.00

To view the information on the R2 device:
show ip router isis

I>* 1.1.1.1/32 [115/13] via 10.1.12.1, eth1, wight 1, 00:19:33
I     10.1.12.0/24  [115/13] via 10.1.12.1, eth1, inactive, wight 1, 00:16:44
I     10.2.12.0/24  [115/13] via 10.1.12.1, eth1, wight 1, 00:16:13
I     10.3.12.0/24  [115/13] via 10.1.12.1, eth1, wight 1, 00:16:13
I     10.4.12.0/24  [115/13] via 10.1.12.1, eth1, wight 1, 00:16:13

In R2, interface eth1 metric set 15, and eth3 metrix 3, the routing should be sent out from eth3 via 10.3.12.1

Version

FRRoting 10.0_git (R2) on Linux(5.15.0-105-generic).
Docker - quay.io/frrouting/frr:10.0.0

How to reproduce

Perform the configuration operations as described.

Expected behavior

Expect to: show ip router isis

I>* 1.1.1.1/32 [115/13] via 10.1.12.1, eth1, wight 1, 00:19:33
I     10.1.12.0/24  [115/13] via 10.3.12.1, eth3, inactive, wight 1, 00:16:44
I     10.2.12.0/24  [115/13] via 10.3.12.1, eth3, wight 1, 00:16:13
I     10.3.12.0/24  [115/13] via 10.3.12.1, eth3, wight 1, 00:16:13
I     10.4.12.0/24  [115/13] via 10.3.12.1, eth3, wight 1, 00:16:13

the routing should be sent out from eth3 via 10.3.12.1

Actual behavior

The routing should be sent out from eth1 via 10.1.12.1

Additional context

No response

Checklist

• I have searched the open issues for this bug.
• I have not included sensitive information in this report.