Please note that you may have a dynamic view per installer, pod or scenario
New Functest dashboard look.
this table reflects the status but it is not dynamically up to date as CI never stops..
We consider hereafter only baremetal scenario.
Icon description:
: 4+ consecutive runs passing the success criteria
: <4 successful consecutive runs but passing the success criteria
: close to pass the success criteria
: 0% success, not passing
POD: ericsson-pod2
source: https://build.opnfv.org/ci/view/functest/job/functest-fuel-ericsson-pod2-daily-brahmaputra/
Scenario ready for Release:
odl_l3 blocked by vPing
bgpvpn not mature
[1]: Detected some errors (~7-8) possibly due to insufficient IPs in the public network ip range. Investigation in progress. Possible fix by Jonas: https://gerrit.opnfv.org/gerrit/#/c/10159/
[2]: It failed 2 times in the last 5 runs.. waiting for more runs to see if it is impracticable. Ashley proposed a patch to fix this and yardstick problems with SSH in this scenario
[3]: last 2 runs it has failed
Scenario ready for Release:
Doctor feature ready for the release
we may assume that nosdn is working but never run in CI
odl_l3 and onos blocked by vPing and Tempest success rate
POD: opnfv-jump-1
source: https://build.opnfv.org/ci/view/functest/job/functest-apex-opnfv-jump-1-daily-brahmaputra/
[1] Nova metadata service is not working properly with ONOS yet. Maybe in SR1.
POD: huawei-us-deploy-bare-1
source: https://build.opnfv.org/ci/view/functest/job/functest-compass-huawei-us-deploy-bare-1-daily-brahmaputra/
Scenarios ready for Release:
Ocl planned for SR1
[1]: There are 11 failed tests out of 210 which (we think) are related to nova metadata service not supported by onos yet. Some tests need to pass the ssh-key to the instances using that service. However, it passes the success criteria of >=90%
POD: orange-pod2
source: https://build.opnfv.org/ci/view/functest/job/functest-joid-orange-pod2-daily-master/
Scenarios ready for Release:
nosdn scenario shall be OK but not run 4 times, will be added next time
vIMS use case fails but it is linked to configuration, solutions are discussed on joid etherpad.
onos scenario (run only 2 times on Orange POD 2) fails due to vPing/ssh
IMPORTANT: intel-pod5 and intel-pod6 won't count for the results report until we fix the possible problems why we get those big timeouts.
POD: intel-pod5
source: https://build.opnfv.org/ci/view/joid/job/functest-joid-intel-pod5-daily-brahmaputra/
[1] Rally takes 4 hr to execute. Something is wrong here…
POD: intel-pod6
source: https://build.opnfv.org/ci/view/functest/job/functest-joid-intel-pod6-daily-master/
[1] No runs found with this scenario on this pod
[2]: It seems the instances don't get an IP from the neutron dhcp agent…