1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
Troubleshooting
===============
This section gives some guidelines about how to troubleshoot the test cases
owned by Functest.
**IMPORTANT**: As in the previous section, the steps defined below must be
executed inside the Functest Docker container and after sourcing the OpenStack credentials::
. $creds
or::
source /home/opnfv/functest/conf/openstack.creds
VIM
---
This section covers the test cases related to the VIM (vPing, Tempest, Rally).
vPing common
^^^^^^^^^^^^
For both vPing test cases (**vPing_ssh**, and **vPing_userdata**), the first steps are
similar:
* Create Glance image
* Create Network
* Create Security Group
* Create instances
After these actions, the test cases differ and will be explained in their respective section.
These test cases can be run inside the container as follows::
$repos_dir/functest/docker/run_tests.sh -t vping_ssh
$repos_dir/functest/docker/run_tests.sh -t vping_userdata
The **run_tests.sh** script is basically calling internally the corresponding
vPing scripts, located in
*$repos_dir/functest/testcases/vPing/CI/libraries/vPing_ssh.py* and
*$repos_dir/functest/testcases/vPing/CI/libraries/vPing_userdata.py* with the
appropriate flags.
After finishing the test execution, the corresponding script will remove all
created resources in OpenStack (image, instances, network and security group).
When troubleshooting, it is advisable sometimes to keep those resources in case the
test fails and a manual testing is needed. This can be achieved by adding the flag *-n*::
$repos_dir/functest/docker/run_tests.sh -n -t vping_ssh
$repos_dir/functest/docker/run_tests.sh -n -t vping_userdata
Some of the common errors that can appear in this test case are::
vPing_ssh- ERROR - There has been a problem when creating the neutron network....
This means that there has been some problems with Neutron, even before creating the
instances. Try to create manually a Neutron network and a Subnet to see if that works.
The debug messages will also help to see when it failed (subnet and router creation).
Example of Neutron commands (using 10.6.0.0/24 range for example)::
neutron net-create net-test
neutron subnet-create --name subnet-test --allocation-pool start=10.6.0.2,end=10.6.0.100 --gateway 10.6.0.254 net-test 10.6.0.0/24
neutron router-create test_router
neutron router-interface-add <ROUTER_ID> test_subnet
neutron router-gateway-set <ROUTER_ID> <EXT_NET_NAME>
Another related error can occur while creating the Security Groups for the instances::
vPing_ssh- ERROR - Failed to create the security group...
In this case, proceed to create it manually. These are some hints::
neutron security-group-create sg-test
neutron security-group-rule-create sg-test --direction ingress --protocol icmp --remote-ip-prefix 0.0.0.0/0
neutron security-group-rule-create sg-test --direction ingress --ethertype IPv4 --protocol tcp --port-range-min 80 --port-range-max 80 --remote-ip-prefix 0.0.0.0/0
neutron security-group-rule-create sg-test --direction egress --ethertype IPv4 --protocol tcp --port-range-min 80 --port-range-max 80 --remote-ip-prefix 0.0.0.0/0
The next step is to create the instances. The image used is located in
*/home/opnfv/functest/data/cirros-0.3.4-x86_64-disk.img* and a Glance image is created
with the name **functest-vping**. If booting the instances fails (i.e. the status
is not **ACTIVE**), you can check why it failed by doing::
nova list
nova show <INSTANCE_ID>
It might show some messages about the booting failure. To try that manually::
nova boot --flavor 2 --image functest-vping --nic net-id=<NET_ID> nova-test
This will spawn a VM using the network created previously manually.
In all the OPNFV tested scenarios from CI, it never has been a problem with the
previous actions. Further possible problems are explained in the following sections.
vPing_SSH
^^^^^^^^^
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/testcases/vPing/CI/libraries/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::
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 flag
*-n* in **run_tests.sh** explained previously) so that the test does not clean
the OpenStack resources. It means that the Container can not reach the public
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 limitation.
First, make sure that the instance **opnfv-vping-2** succeeded to get an IP from
the DHCP agent. It can be checked by doing::
nova console-log opnfv-vping-2
If the message *Sending discover* and *No lease, failing* is shown, it probably
means that the Neutron dhcp-agent failed to assign an IP or even that it was not
responding. At this point it does not make sense to try to ping the floating IP.
If the instance got an IP properly, try to ping manually the VM from the container::
nova list
<grab the public IP>
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 rules because
there might be some rules rejecting ICMP or TCP traffic coming/going from/to the container.
At this point, if the ping does not work either, try to reproduce the test
manually with the steps described above in the vPing common section with the addition::
neutron floatingip-create <EXT_NET_NAME>
nova floating-ip-associate nova-test <FLOATING_IP>
Further troubleshooting is out of scope of this document, as it might be due to
problems with the SDN controller. Contact the installer team members or send an
email to the corresponding OPNFV mailing list for more information.
vPing_userdata
^^^^^^^^^^^^^^
This test case does not create any floating IP neither establishes an SSH
connection. Instead, it uses nova-metadata service when creating an instance
to pass the same script as before (ping.sh) but as 1-line text. This script
will be executed automatically when the second instance **opnfv-vping-2** is booted.
The only known problem here for this test to fail is mainly the lack of support
of cloud-init (nova-metadata service). Check the console of the instance::
nova console-log opnfv-vping-2
If this text or similar is shown::
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 1.13. request failed
failed 2/20: up 13.18. request failed
failed 3/20: up 25.20. request failed
failed 4/20: up 37.23. request failed
failed 5/20: up 49.25. request failed
failed 6/20: up 61.27. request failed
failed 7/20: up 73.29. request failed
failed 8/20: up 85.32. request failed
failed 9/20: up 97.34. request failed
failed 10/20: up 109.36. request failed
failed 11/20: up 121.38. request failed
failed 12/20: up 133.40. request failed
failed 13/20: up 145.43. request failed
failed 14/20: up 157.45. request failed
failed 15/20: up 169.48. request failed
failed 16/20: up 181.50. request failed
failed 17/20: up 193.52. request failed
failed 18/20: up 205.54. request failed
failed 19/20: up 217.56. request failed
failed 20/20: up 229.58. request failed
failed to read iid from metadata. tried 20
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 scenario dealing with ONOS and the tests have been
excluded from CI in those scenarios.
Tempest
^^^^^^^
In the upstream OpenStack CI all the Tempest test cases are supposed to pass.
If some test cases fail in an OPNFV deployment, the reason is very probably one
of the following
+-----------------------------+------------------------------------------------+
| Error | Details |
+=============================+================================================+
| Resources required for test | Such resources could be e.g. an external |
| case execution are missing | network and access to the management subnet |
| | (adminURL) from the Functest docker container. |
+-----------------------------+------------------------------------------------+
| OpenStack components or | Check running services in the controller and |
| services are missing or not | compute nodes (e.g. with "systemctl" or |
| configured properly | "service" commands). Configuration parameters |
| | can be verified from related .conf files |
| | located under /etc/<component> directories. |
+-----------------------------+------------------------------------------------+
| Some resources required for | The tempest.conf file, automatically generated |
| execution test cases are | by Rally in Functest, does not contain all the |
| missing | needed parameters or some parameters are not |
| | set properly. |
| | The tempest.conf file is located in /home/opnfv|
| | /.rally/tempest/for-deployment-<UUID> in |
| | Functest container |
| | Use "rally deployment list" command in order to|
| | check UUID of current deployment. |
+-----------------------------+------------------------------------------------+
When some Tempest test case fails, captured traceback and possibly also related
REST API requests/responses are output to the console.
More detailed debug information can be found from tempest.log file stored into
related Rally deployment folder.
Rally
^^^^^
Same error causes than for Tempest mentioned above may lead to errors in Rally.
It is possible to run only one Rally scenario, instead of the whole suite.
To do that, call the python script (instead of *run_tests.sh*) as follows::
python $repos_dir/functest/testcases/VIM/OpenStack/CI/libraries/run_rally-cert.py -h
usage: run_rally-cert.py [-h] [-d] [-r] [-s] [-v] [-n] test_name
positional arguments:
test_name Module name to be tested. Possible values are : [
authenticate | glance | cinder | heat | keystone | neutron |
nova | quotas | requests | vm | all ] The 'all' value
performs all possible test scenarios
optional arguments:
-h, --help show this help message and exit
-d, --debug Debug mode
-r, --report Create json result file
-s, --smoke Smoke test mode
-v, --verbose Print verbose info about the progress
-n, --noclean Don't clean the created resources for this test.
For example, to run the Glance scenario with debug information::
python $repos_dir/functest/testcases/VIM/OpenStack/CI/libraries/run_rally-cert.py -d glance
Possible scenarios are:
* authenticate
* glance
* cinder
* heat
* keystone
* neutron
* nova
* quotas
* requests
* vm
To know more about what those scenarios are doing, they are defined in:
*$repos_dir/functest/testcases/VIM/OpenStack/CI/suites*. For more info about
Rally scenario definition please refer to the Rally official documentation.
If the flag *all* is specified, it will run all the scenarios one by one. Please
note that this might take some time (~1,5hr), taking around 1 hour to complete the
Nova scenario.
To check any possible problems with rally, the logs are stored under
*/home/opnfv/functest/results/rally/* in the Functest container.
Controllers
-----------
ODL
^^^
2 versions are supported in Brahmaputra depending on the scenario:
* Lithium
* Berylium
The upstream test suites have not been adapted, so you may get 18 or 15 tests
passed on 18 depending on your configuration. The 3 testcases are partly failed
due to wrong return code.
ONOS
^^^^
Please refer to the ONOS documentation.
OpenContrail
^^^^^^^^^^^^
Feature
-------
vIMS
^^^^
vIMS deployment may fail for several reasons, the most frequent ones are
described in the following table:
+-----------------------------------+------------------------------------+
| Error | Comments |
+===================================+====================================+
| Keystone admin API not reachable | Impossible to create vIMS user and |
| | tenant |
+-----------------------------------+------------------------------------+
| Impossible to retrieve admin role | Impossible to create vIMS user and |
| id | tenant |
+-----------------------------------+------------------------------------+
| Error when uploading image from | impossible to deploy VNF |
| OpenStack to glance | |
+-----------------------------------+------------------------------------+
| Cinder quota cannot be updated | Default quotas not sufficient, they|
| | are adapted in the script |
+-----------------------------------+------------------------------------+
| Impossible to create a volume | VNF cannot be deployed |
+-----------------------------------+------------------------------------+
| SSH connection issue between the | if vPing test fails, vIMS test will|
| Test container and the VM | fail... |
+-----------------------------------+------------------------------------+
| No Internet access from a VM | the VMs of the VNF must have an |
| | external access to Internet |
+-----------------------------------+------------------------------------+
Promise
^^^^^^^
Please refer to the Promise documentation.
|
