aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMorgan Richomme <morgan.richomme@orange.com>2016-08-30 09:01:31 +0200
committerJose Lausuch <jose.lausuch@ericsson.com>2016-08-30 16:05:42 +0000
commite1cf8564b1f06a64863ee463b817935ec58f834c (patch)
tree673535e02d1dd76bf908c74928b0967aca00d97d
parent029a659b4198611dc93b6b41f42c3939a98de5bd (diff)
Release note: add restriction for joid/domino
JIRA: FUNCTEST-436 Change-Id: I44fb50a2ef58095aff54f03b837bf456850f3057 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
-rw-r--r--docs/configguide/configguide.rst2
-rw-r--r--docs/release-notes/functest-release.rst30
2 files changed, 20 insertions, 12 deletions
diff --git a/docs/configguide/configguide.rst b/docs/configguide/configguide.rst
index 4d0d35b7..d7949439 100644
--- a/docs/configguide/configguide.rst
+++ b/docs/configguide/configguide.rst
@@ -18,7 +18,7 @@ release installed in your environment. All available tagged images can
be seen from location [FunctestDockerTags_]. For example, when running
on the first official release of the OPNFV Colorado system platform,
tag "colorado.1.0" is needed. Pulling other tags might cause some
-problems while running the tests.
+problems while running the tests.
Docker images pulled without a tag specifier bear the implicitly
assigned label "latest". If you need to specifically pull the latest
Functest docker image, then omit the tag argument::
diff --git a/docs/release-notes/functest-release.rst b/docs/release-notes/functest-release.rst
index 508f6e2a..6ebab22a 100644
--- a/docs/release-notes/functest-release.rst
+++ b/docs/release-notes/functest-release.rst
@@ -232,8 +232,8 @@ The reporting pages can be found at:
* fuel: http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-fuel.html
* joid: http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-joid.html
-Colorado known issues
-=====================
+Colorado known restrictions/issues
+==================================
+-----------+-----------+----------------------------------------------+
| Installer | Scenario | Issue |
@@ -242,16 +242,17 @@ Colorado known issues
| | | metadata service excluded from onos scenarios|
| | | https://gerrit.opnfv.org/gerrit/#/c/18729/ |
+-----------+-----------+----------------------------------------------+
-| joid | any | Tempest cases related to storage excluded |
-| | | https://gerrit.opnfv.org/gerrit/#/c/17871/ |
-+-----------+-----------+----------------------------------------------+
-| fuel | any | TestServerBasicOps test case skipped |
-| | | https://gerrit.opnfv.org/gerrit/#/c/19635/ |
-+-----------+-----------+----------------------------------------------+
| apex/fuel | *-bgpvpn | vPing_ssh (floating ips not supported) and |
| | | vIMS excluded. Some Tempest cases related to |
| | | floating ips also excluded. |
+-----------+-----------+----------------------------------------------+
+| compass | moon | First ODL test FAILS because ODL/Openstack |
+| | | federation done in moon is partial. Only |
+| | | MD-SAL is federated (not AD-SAL) |
++-----------+-----------+----------------------------------------------+
+| fuel | any | TestServerBasicOps test case skipped |
+| | | https://gerrit.opnfv.org/gerrit/#/c/19635/ |
++-----------+-----------+----------------------------------------------+
| fuel | kvm | vPing_ssh and vIMS excluded (metadata related|
| | | scenarios) |
+-----------+-----------+----------------------------------------------+
@@ -263,9 +264,16 @@ Colorado known issues
| | | workaround consists in restarting memcache on|
| | | server |
+-----------+-----------+----------------------------------------------+
-| compass | moon | First ODL test FAILS because ODL/Openstack |
-| | | federation done in moon is partial. Only |
-| | | MD-SAL is federated (not AD-SAL) |
+| joid | any | Tempest cases related to object storage |
+| | | excluded |
+| | | https://gerrit.opnfv.org/gerrit/#/c/17871/ |
++-----------+-----------+----------------------------------------------+
+| joid | domino | Domino tests are skipped in CI. However the |
+| | | test case can be run by manually setting |
+| | | IS_IPandKEY_CONFIGURED=true after manually |
+| | | setting properly the IP addresses of the 3 |
+| | | Controller nodes in the configuration file |
+| | | /repos/domino/tests/run_multinode.sh |
+-----------+-----------+----------------------------------------------+