summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/userguide/troubleshooting.rst
diff options
context:
space:
mode:
authorMorgan Richomme <morgan.richomme@orange.com>2017-09-12 11:39:11 +0200
committerJose Lausuch <jalausuch@suse.com>2017-10-11 14:04:18 +0000
commit21d8ff3fb13dac52cb3e906e968ee69104012082 (patch)
tree4ea58dbf17e4ed2e31fc86d744a103ed94a749f6 /docs/testing/user/userguide/troubleshooting.rst
parentb45746ee8dcf62cf11b860e4c4b797779a08abc7 (diff)
Update Functest documentation for Euphrates
- Better description of Alpine docker (default artifact) - Reorganization of config and user guide - Upgrade of the developer guide Change-Id: Ie8e10f027bfcdb01c992cd161a1af2d6d6e29536 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com> (cherry picked from commit 5504724dc69096b36948de9bd07b82f5058242f0)
Diffstat (limited to 'docs/testing/user/userguide/troubleshooting.rst')
-rw-r--r--docs/testing/user/userguide/troubleshooting.rst30
1 files changed, 12 insertions, 18 deletions
diff --git a/docs/testing/user/userguide/troubleshooting.rst b/docs/testing/user/userguide/troubleshooting.rst
index 1c5166081..29facc294 100644
--- a/docs/testing/user/userguide/troubleshooting.rst
+++ b/docs/testing/user/userguide/troubleshooting.rst
@@ -43,9 +43,9 @@ These test cases can be run inside the container, using new Functest CLI as foll
$ functest testcase run vping_userdata
The Functest CLI is designed to route a call to the corresponding internal
-python scripts, located in paths:
-*$REPOS_DIR/functest/functest/opnfv_tests/openstack/vping/vping_ssh.py* and
-*$REPOS_DIR/functest/functest/opnfv_tests/openstack/vping/vping_userdata.py*
+python scripts, located in paths
+/usr/lib/python2.7/site-packages/functest/opnfv_tests/openstack/vping/vping_ssh.py
+and /usr/lib/python2.7/site-packages/functest/opnfv_tests/openstack/vping/vping_userdata.py
Notes:
@@ -122,9 +122,10 @@ This test case creates a floating IP on the external network and assigns it to
the second instance **opnfv-vping-2**. The purpose of this is to establish
a SSH connection to that instance and SCP a script that will ping the first
instance. This script is located in the repository under
-*$REPOS_DIR/functest/functest/opnfv_tests/openstack/vping/ping.sh* and takes an IP as
-a parameter. When the SCP is completed, the test will do an SSH call to that script
-inside the second instance. Some problems can happen here::
+/usr/lib/python2.7/site-packages/functest/opnfv_tests/openstack/vping/ping.sh
+and takes an IP as a parameter. When the SCP is completed, the test will do a
+SSH call to that script inside the second instance. Some problems can happen
+here::
vPing_ssh- ERROR - Cannot establish connection to IP xxx.xxx.xxx.xxx. Aborting
@@ -210,9 +211,6 @@ If this text or similar is shown::
it means that the instance failed to read from the metadata service. Contact
the Functest or installer teams for more information.
-NOTE: Cloud-init in not supported on scenarios dealing with ONOS and the tests
-have been excluded from CI in those scenarios.
-
Tempest
^^^^^^^
@@ -238,7 +236,7 @@ of the following
| execution test cases are | Rally in Functest, does not contain all the needed |
| missing | parameters or some parameters are not set properly. |
| | The tempest.conf file is located in directory |
-| | '/home/opnfv/.rally/verification/verifier-<UUID> |
+| | 'root/.rally/verification/verifier-<UUID> |
| | /for-deployment-<UUID>' |
| | in the Functest Docker container. Use the "rally |
| | deployment list" command in order to check the UUID |
@@ -266,12 +264,12 @@ Possible scenarios are:
* keystone
* neutron
* nova
+ * ceilometer
* quotas
- * requests
* vm
To know more about what those scenarios are doing, they are defined in directory:
-*$REPOS_DIR/functest/functest/opnfv_tests/openstack/rally/scenario*
+/usr/lib/python2.7/site-packages/functest/opnfv_tests/openstack/rally/scenario
For more info about Rally scenario definition please refer to the Rally official
documentation. `[3]`_
@@ -295,10 +293,6 @@ If any of the other test cases fails, check that Neutron and ODL have
been correctly configured to work together. Check Neutron configuration
files, accounts, IP addresses etc.).
-ONOS
-^^^^
-Please refer to the ONOS documentation. `ONOSFW User Guide`_ .
-
Features
--------
@@ -306,7 +300,6 @@ Features
Please refer to the dedicated feature user guides for details.
-
VNF
---
@@ -342,6 +335,7 @@ described in the following table:
| the VM | the vIMS VNF installation fails |
+-----------------------------------+------------------------------------+
-
+Please note that this test case requires resources (8 VM (2Go) + 1 VM (4Go)), it
+is there fore not recommended to run it on a light configuration.
.. _`OPNFV Functest Developer Guide`: http://artifacts.opnfv.org/functest/docs/devguide/#