FIX: Interface up handling 62/13662/16
authorPeter Mikus <pmikus@cisco.com>
Wed, 25 Jul 2018 06:47:34 +0000 (06:47 +0000)
committerPeter Mikus <pmikus@cisco.com>
Fri, 27 Jul 2018 22:09:46 +0000 (22:09 +0000)
commit584345da4f7330f7517e5defd894b4995c2b57b0
treedf9a146150036940b1245b57555564cdf0de9961
parentaee34715f8aab82f25cf5c2b5aa696c4c65c3ea9
FIX: Interface up handling

- Increase timeout when trying to check interface (this is useful if
there are multiple interfaces and dump command take more than
TIMEOUT/NR_IF which is happening quite often).
- Reverse the order of applying MTU and interface UP to try to prevent
API overload during interface initialization phase.

Change-Id: I4e8623963d15b3c0d202172b4c58c43a972bb9cb
Signed-off-by: Peter Mikus <pmikus@cisco.com>
19 files changed:
resources/libraries/python/ContainerUtils.py
resources/libraries/python/InterfaceUtil.py
resources/libraries/robot/performance/performance_configuration.robot
resources/libraries/robot/shared/container.robot
resources/libraries/robot/tcp/tcp_setup.robot
tests/vpp/perf/l2/25ge2p1xxv710-eth-l2patch-mrr.robot
tests/vpp/perf/l2/25ge2p1xxv710-eth-l2patch-ndrpdr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2bdbasemaclrn-mrr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2bdbasemaclrn-ndrpdr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2patch-mrr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2patch-ndrpdr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2xcbase-mrr.robot
tests/vpp/perf/l2/2n1l-25ge2p1xxv710-eth-l2xcbase-ndrpdr.robot
topologies/available/lf_2n_skx_testbed21.yaml
topologies/available/lf_2n_skx_testbed22.yaml
topologies/available/lf_2n_skx_testbed23.yaml
topologies/available/lf_2n_skx_testbed24.yaml
topologies/available/lf_3n_skx_testbed31.yaml
topologies/available/lf_3n_skx_testbed32.yaml