[LU-13364] lnetctl: unexpected output for lnetctl import --show Created: 17/Mar/20 Updated: 16/Oct/22 Resolved: 16/Oct/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Cyril Bordage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | easy, lnet | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
nid entries at the end of the net show is extraneous. They shouldn't be there.
[root@lustre02 ~]# lnetctl import --show < net984481795.yaml
net:
- net type: lo
local NI(s):
- nid: 0@lo
status: up
- net type: tcp
local NI(s):
- nid: 192.168.122.103@tcp
status: up
interfaces:
0: eth0
- nid: 192.168.122.104@tcp
status: up
interfaces:
0: eth1
- nid: 192.168.122.105@tcp
status: up
interfaces:
0: eth2
- net type: tcp2
local NI(s):
- nid: 192.168.122.103@tcp2
status: up
interfaces:
0: eth0
- net type: tcp3
local NI(s):
- nid: 192.168.122.103@tcp3
status: up
interfaces:
0: eth0
- net type: tcp4
local NI(s):
- nid: 192.168.122.103@tcp4
status: up
interfaces:
0: eth0
- nid: 0@lo
status: up
- nid: 0@lo
status: up
|
| Comments |
| Comment by Cyril Bordage [ 19/Oct/20 ] |
|
Do we need to merge imported config and detected config? Right now, if we have "net" node in imported config, we kind of a merge (with a bad node). Do I need to merge with absent interfaces? |
| Comment by Gerrit Updater [ 04/Jun/21 ] |
|
Cyril Bordage (cbordage@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/43922 |
| Comment by Gerrit Updater [ 15/Oct/22 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/43922/ |
| Comment by Peter Jones [ 16/Oct/22 ] |
|
Landed for 2.16 |