diff options
| author |   Cédric Ollivier <cedric.ollivier@orange.com> | 2019-10-17 20:53:04 +0200 |
|---|---|---|
| committer | Cédric Ollivier <cedric.ollivier@orange.com> | 2019-10-19 17:31:15 +0200 |
| commit | 841894cc1aba5ee90ad01a4b0d65f741c54be498 (patch) | |
| tree | f79be80b85be1c64e7ce184c46d802782b17e25f /docs/testing/user/userguide/troubleshooting.rst | |
| parent | 7ad64e6e4030b42e256f7a6661fce61d68860439 (diff) | |
Check spelling in rst files
It fixes a few typos too and installs enchant in TravisCI and CircleCI
jobs.
Change-Id: Id5dbf5f926edc8b0b4e4337d11bf63e21ea7e173
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit 83aa78773dd0fea7064b8fa9676c44c061dc5e66)
Diffstat (limited to 'docs/testing/user/userguide/troubleshooting.rst')
| -rw-r--r-- | docs/testing/user/userguide/troubleshooting.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/testing/user/userguide/troubleshooting.rst b/docs/testing/user/userguide/troubleshooting.rst index 279a47398..7c54cba56 100644 --- a/docs/testing/user/userguide/troubleshooting.rst +++ b/docs/testing/user/userguide/troubleshooting.rst @@ -133,8 +133,8 @@ here:: vPing_ssh- ERROR - Cannot establish connection to IP xxx.xxx.xxx.xxx. Aborting If this is displayed, stop the test or wait for it to finish, if you have used -the special method of test invocation with specific supression of OpenStack -resource clean-up, as explained earler. It means that the Container can not +the special method of test invocation with specific suppression of OpenStack +resource clean-up, as explained earlier. It means that the Container can not reach the Public/External IP assigned to the instance **opnfv-vping-2**. There are many possible reasons, and they really depend on the chosen scenario. For most of the ODL-L3 and ONOS scenarios this has been noticed and it is a known @@ -158,7 +158,7 @@ container:: ping <public IP> If the ping does not return anything, try to ping from the Host where the -Docker container is running. If that solves the problem, check the iptable +Docker container is running. If that solves the problem, check the iptables rules because there might be some rules rejecting ICMP or TCP traffic coming/going from/to the container. |