[SDNVPN] Disable Rally Sanity test case for bgpvpn scenarios

Due to a known issue with API performance when bgpvpn extension
is activated which causes some delays and the tests take longer
time than normal, we get a lot of Jenkins Job timeouts and the
scenario cannot be validated.
Since it is a performance issue, we black list rally sanity, which
takes 1 hour to complete and will re-enable it in Colorado.2.0
where ODL Boron release will be available and SDNVPN team
thinks this will be fixed.

Change-Id: Idc68e30ea15d52d0fd4b63bc57ddf643f3f7c8b4
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
(cherry picked from commit 642661f2de6afa12268e2d2cb854652f3db10ab8)

diff --git a/ci/testcases.yaml b/ci/testcases.yaml
index 4fcdd1b..3b76e13 100644 (file)
--- a/ci/testcases.yaml
+++ b/ci/testcases.yaml
@@ -71,7 +71,7 @@ tiers:
                     Rally suite in smoke mode.
                 dependencies:
                     installer: ''
-                    scenario: ''
+                    scenario: '^((?!bgpvpn).)*$'
 
     -
         name: sdn_suites

diff --git a/docs/release-notes/functest-release.rst b/docs/release-notes/functest-release.rst
index 9623b43..816ed74 100644 (file)
--- a/docs/release-notes/functest-release.rst
+++ b/docs/release-notes/functest-release.rst
@@ -251,7 +251,15 @@ Colorado known restrictions/issues
 +-----------+-----------+----------------------------------------------+
 | apex/fuel | *-bgpvpn  | vPing_ssh (floating ips not supported) and   |
 |           |           | vIMS excluded. Some Tempest cases related to |
-|           |           | floating ips also excluded.                  |
+|           |           | floating ips also excluded. Some performance |
+|           |           | issues have been detected in this scenario   |
+|           |           | (i.e. BGPVPN extension enabled) when running |
+|           |           | commands against the OpenStack APIs, thus    |
+|           |           | Rally sanity test case has been disabled.    |
+|           |           | Performance issues seem to be connected to   |
+|           |           | the ODL version. It is planned to reintroduce|
+|           |           | Rally sanity in Colorado 2.0 with the        |
+|           |           | adoption of ODL Boron release.               |
 +-----------+-----------+----------------------------------------------+
 | compass   | moon      | First ODL test FAILS because ODL/Openstack   |
 |           |           | federation done in moon is partial. Only     |