[LU-13790] socklnd: NID to interface mapping issues Created: 15/Jul/20 Updated: 07/Aug/20 Resolved: 07/Aug/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Serguei Smirnov | Assignee: | Serguei Smirnov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Severity: | 3 | ||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||
| Description |
|
Testing showed that NID to interface mapping was still wrong after
# lnetctl lnet configure
# lnetctl net add --net tcp --if eth0,eth1,eth2
# lnetctl discover <MR peer NID>
# lnetctl ping <MR peer NID>
Discovery would succeed, but first ping would fail as a NID on an interface other than the first would be picked to send out the ping and the mapping for the NID was wrong. |
| Comments |
| Comment by Gerrit Updater [ 16/Jul/20 ] |
|
Serguei Smirnov (ssmirnov@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/39408 |
| Comment by Gerrit Updater [ 07/Aug/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39408/ |
| Comment by Peter Jones [ 07/Aug/20 ] |
|
Landed for 2.14 |