[LU-13713] LNet Router: bug in the predetermined gateway case Created: 24/Jun/20 Updated: 11/Jul/20 Resolved: 11/Jul/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Amir Shehata (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
If the gateway is predetermined the code shortcuts looking up the route. Therefore it is possible that the route has been removed, but the gateway peer is still in our database, which would lead us to respond over that gateway, even though there is no route that exists to it. We should only use the peer specified by the rtr_nid if it's a gateway. Otherwise we should lookup an alternative path. We shouldn't quit right away. There could exist other routed paths to the destination. |
| Comments |
| Comment by Gerrit Updater [ 25/Jun/20 ] |
|
Amir Shehata (ashehata@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/39175 |
| Comment by Gerrit Updater [ 10/Jul/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39175/ |
| Comment by Peter Jones [ 11/Jul/20 ] |
|
Landed for 2.14 |