Sorry for the late response.
Per #1 the ssh timeout for onos/onos-sfc cases was due to the wrong OVS build
being used for those scenarios. It was fixed last night, and yardstick seems
to be running OK:
There is still a bug here with ONOS and DHCP though where functest fails. I
found the following traceback https://paste.fedoraproject.org/432623/raw/.
Michael and I are debugging it, it looks to be a race condition.
For ODL-L3, floating ip wont work due to a known bug (for any installer) in ODL
Per #2 - I think the issue here is that the deploy failed so there is no
We don't abort the daily job if a deploy fails, we just let the subsequent jobs
Red Hat SDN Team
----- Original Message -----
From: "chenjiankun" <chenjiank...@huawei.com>
Cc: "Gaoliang (kubi)" <jean.gaoli...@huawei.com>,
email@example.com, "Wei Su (Su)" <su....@huawei.com>
Sent: Sunday, September 18, 2016 1:03:35 AM
Subject: [yardstick][apex]Testcase run error in yardstick apex ci
I am a contributor in yardstick.
I find two problems in yardstick apex ci:
1. SSHTimeout, in the error log I find "SSHTimeout, Timeout waiting for
'172.30.9.205'", the problem appear in os-onos-sfc-ha, os-onos-nofeature-ha,
In this test case, yardstick ssh a floating ip.I don know where this problem
is. Could you please help me to check?
2. OS_AUTH_URL is unset or empty, in the error log I find "scp:
/home/stack/overcloudrc: No such file or directory", this problem appear in
os-nosdn-ovs-noha, os-odl_l2-sfc-noha scenarios.
This problem occur when yardstick run "sudo scp $ssh_options
Does the path not in the pod? Or any one modify it?
opnfv-tech-discuss mailing list