== sanity-lnet test 214: Check local NI status when link is downed ========================================================== 10:31:12 (1729607472)
Cleaning up LNet
Writer error: failed to resolve Netlink family id
unloading modules on: 'oleg221-server'
oleg221-server: oleg221-server.virtnet: executing unload_modules_local
oleg221-server: LNET unconfigure error 22: Invalid argument
modules unloaded.
ip link add 'test1pl' type veth peer name test1pg 
RTNETLINK answers: File exists
ip link set 'test1pl' up
 ip addr add "10.1.2.3/31" dev test1pg
RTNETLINK answers: File exists
 ip -6 addr add "2001:db8:0:f101::1/64" dev test1pg
RTNETLINK answers: File exists
 ip link set test1pg up
Loading LNet and configuring DLC
Loading modules from /home/green/git/lustre-release/lustre
detected 4 online CPUs by sysfs
Force libcfs to create 2 CPU partitions
../libcfs/libcfs/libcfs options: 'cpu_npartitions=2'
/home/green/git/lustre-release/lustre/../lnet/utils/lnetctl lnet configure
/home/green/git/lustre-release/lustre/../lnet/utils/lnetctl net add --net tcp --if eth0
default via 192.168.202.254 dev eth0
/home/green/git/lustre-release/lustre/../lnet/utils/lnetctl net add --net tcp --if test1pg
default via 192.168.202.254 dev eth0
10.1.2.2/31 dev test1pg proto kernel scope link src 10.1.2.3
NI 0@lo expect status "up" found "up"
NI 192.168.202.21@tcp expect status "up" found "up"
NI 10.1.2.3@tcp expect status "up" found "up"
/home/green/git/lustre-release/lustre/../lnet/utils/lnetctl ping --source 10.1.2.3@tcp 192.168.202.21@tcp
ping:
- primary nid: 192.168.202.21@tcp
  Multi-Rail: false
  peer_ni:
  - nid: 192.168.202.21@tcp
  - nid: 10.1.2.3@tcp
Set test1pg down
ip link set dev test1pg down
NI 0@lo expect status "up" found "up"
NI 192.168.202.21@tcp expect status "up" found "up"
NI 10.1.2.3@tcp expect status "down" found "down"
pdsh@oleg221-client: oleg221-server: ssh exited with exit code 2
pdsh@oleg221-client: oleg221-server: ssh exited with exit code 2