[LU-14945] LNet: don't use hops to determine whether the route is up or down

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.15.0
• Type: Bug
• Priority: Minor
• Reporter: Serguei Smirnov
• Assignee: Serguei Smirnov
• Resolution: Fixed
• Severity: 3

Description

 NodeA <-tcp1-> GW1 <-tcp2-> GW2 <-tcp3-> NodeB

Assuming GW1 knows how to reach tcp3 network and GW2 knows how to reach tcp1 network, it should be possible to add routes without specifying hop count = 2 on nodes A and B to reach tcp3 and tcp1 respectively and then be able to lnetctl ping between them. Changes introduced by LU-13785 interpret default hops to be equivalent to hops = 1 set explicitly for the purpose of determining route aliveness, which results in the routes created as described above to be considered "down". Fix it so that default hop setting doesn't prevent the multi-hop scenario from working.

Comments

[Gerrit Updater]

"Serguei Smirnov <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/44674
Subject: LU-14945 lnet: don't use hops to determine the route state
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 221d6e09dbde9716a8d06fea765012923856e600

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/44674/
Subject: LU-14945 lnet: don't use hops to determine the route state
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 3f2844dc9333c86452c37bd7b4519729b1351371

[Peter Jones]

Landed for 2.15