[LU-17230] socklnd: treat UNKNOWN netif operational state as UP rather than DOWN Created: 26/Oct/23 Updated: 11/Dec/23 Resolved: 29/Nov/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Serguei Smirnov | Assignee: | Serguei Smirnov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | lnet, lnet-health, socklnd | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
"UNKNOWN" (IF_OPER_UNKNOWN) operational state doesn't necessarily mean that the interface can't be used and may be the result of particular network driver not providing UP/DOWN states, so it may be incorrect for socklnd to initiate setting of a "fatal error" flag on a NI using an interface in "UNKNOWN" operstate. |
| Comments |
| Comment by Gerrit Updater [ 26/Oct/23 ] |
|
"Serguei Smirnov <ssmirnov@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/52842 |
| Comment by Gerrit Updater [ 29/Nov/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/52842/ |
| Comment by Peter Jones [ 29/Nov/23 ] |
|
Landed for 2.16 |