Don't filter vs NO_TENANT_NETWORK in CNTT testcases

This param is incorrect from a CNTT point of view.
It only filters test cases in classical IaaS verification containers.

Change-Id: I8551cb1af28ecb2bea5c29d7c0b692fee41bd119
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit d96dde8a04a7787a44a9b4fd5d447f6ffb6acb2b)

diff --git a/docker/benchmarking-cntt/testcases.yaml b/docker/benchmarking-cntt/testcases.yaml
index 9c382c7..30eb3e6 100644 (file)
--- a/docker/benchmarking-cntt/testcases.yaml
+++ b/docker/benchmarking-cntt/testcases.yaml
@@ -50,8 +50,6 @@ tiers:
                     VMTP is a small python application that will automatically
                     perform ping connectivity, round trip time measurement
                     (latency) and TCP/UDP throughput
-                dependencies:
-                    - NO_TENANT_NETWORK: '^(?![tT]rue$)'
                 run:
                     name: vmtp
 
@@ -65,7 +63,5 @@ tiers:
                     like iperf, iperf3 and netperf (with help of flent). Shaker
                     is able to deploy OpenStack instances and networks in
                     different topologies.
-                dependencies:
-                    - NO_TENANT_NETWORK: '^(?![tT]rue$)'
                 run:
                     name: shaker