summaryrefslogtreecommitdiffstats
path: root/tests/opnfv/test_cases/opnfv_yardstick_tc070.yaml
diff options
context:
space:
mode:
authorAlexandru Nemes <alexandru.nemes@enea.com>2017-06-27 14:05:07 +0300
committerAlexandru Nemes <alexandru.nemes@enea.com>2017-07-03 11:38:15 +0000
commit30e5dff43e69e958ff73c807eecdd1dcf20764a8 (patch)
tree42e4a3278742ac40484a5f150db3ac7ba5e7bb1b /tests/opnfv/test_cases/opnfv_yardstick_tc070.yaml
parent0367765435e89f1590c6db25b74880b8014164c8 (diff)
Blacklist TC011 from suites with ODL
In deployments with ODL, security groups behave badly because of an IPv6 rule that causes IPv4 packets to be incorrectly routed. This is described in: https://jira.opnfv.org/browse/ARMBAND-61 As a consequence, Yardstick TC011 fails because iperf cannot create a connection. The proposed solution is to temporarily comment out TC011 from test suites with ODL. As mentioned here, security groups support for IPv6 is partial: artifacts.opnfv.org/ipv6/docs/gapanalysis/gap-analysis-odl-boron.html On nosdn deployments this issue is not reproducing and the test runs ok. JIRA: ARMBAND-269 Change-Id: Id5fede27262c21d777ec8e9988941643d16f9417 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
Diffstat (limited to 'tests/opnfv/test_cases/opnfv_yardstick_tc070.yaml')
0 files changed, 0 insertions, 0 deletions