== sanity-lnet test 290: Check that lnet acceptor is using explicit address binding ========================================================== 23:06:44 (1764734804)
Cleaning up LNet
/home/green/git/lustre-release/lustre/scripts/lustre_rmmod: line 114: echo: write error: Device or resource busy
LNET unconfigure error 22: Invalid argument
/home/green/git/lustre-release/lustre/scripts/lustre_rmmod: line 156: echo: write error: Device or resource busy
unloading modules via unload_modules_local on: 'oleg409-server'
oleg409-server: oleg409-server.virtnet: executing unload_modules_local
oleg409-server: /home/green/git/lustre-release/lustre/scripts/lustre_rmmod: line 114: echo: write error: Device or resource busy
oleg409-server: LNET unconfigure error 22: Invalid argument
oleg409-server: /home/green/git/lustre-release/lustre/scripts/lustre_rmmod: line 156: echo: write error: Device or resource busy
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
 ip link set test1pg up
Waiting 10s for '0'
Updated after 2s: want '0' got '0'
Loading LNet and configuring DLC
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 1033: echo: write error: Device or resource busy
/home/green/git/lustre-release/lustre/tests/test-framework.sh: line 1034: echo: write error: Device or resource busy
Loading modules from /home/green/git/lustre-release/lustre
detected 4 online CPUs by sysfs
MODOPTS_LIBCFS=
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
pdsh@oleg409-client: oleg409-server: ssh exited with exit code 2
pdsh@oleg409-client: oleg409-server: ssh exited with exit code 2