-
Notifications
You must be signed in to change notification settings - Fork 1k
lag_2 test hangup in t1-64-lag #910
Description
Hello,
I try to run lag_2 test in t1-64-lag topology, but it always hangup at lag_run_ptf.yml:10:
TASK [test : Run lag_test.LacpTimingTest on PTF docker.] ***********************
task path: /var/polly_hsu/sonic-mgmt/ansible/roles/test/tasks/lag_run_ptf.yml:10
Thursday 09 May 2019 19:05:25 +0000 (0:00:01.324) 1:47:15.230 **********
<10.250.0.246> ESTABLISH SSH CONNECTION FOR USER: root
<10.250.0.246> SSH: EXEC sshpass -d15 ssh -C -vvv -o ControlMaster=auto -o ControlPersist=120s -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o User=root -o ConnectTimeout=10 -o ControlPath=/var/polly_hsu/.ansible/cp/ansible-ssh-%h-%p-%r 10.250.0.246 'LANG=C LC_ALL=C LC_MESSAGES=C /usr/bin/python'
I check lag_2.yml, it has included testbed topology configuration for t1-lag, t0, and t0-116.
Is it the reason for the hangup in t1-64-lag? (No problem when running lag_2 in t0 or t1-lag)
-
name: Include testbed topology configuration (to get LAG IP and PTF docker interfaces, that are behind LAG VMs).
include_vars: vars/topo_t1-lag.yml
when: testbed_type == 't1-lag' -
name: Include testbed topology configuration (to get LAG IP and PTF docker interfaces, that are behind LAG VMs).
include_vars: vars/topo_t0.yml
when: testbed_type == 't0' -
name: Include testbed topology configuration (to get LAG IP and PTF docker interfaces, that are behind LAG VMs).
include_vars: vars/topo_t0-116.yml
when: testbed_type == 't0-116'
Please advise.
Thanks a lot!