mardi 25 août 2015

Openstack Tempest does not run tests after rebooting devstack server

I have a server where is installed devstack.
All service run successfully.
And I need to run Tempest test on that server.
The first time after install devstack, the Tempest run tests successfully. But after I reboot server, Tempest no run the tests (I started all service successfully in devstack by running rejoin-stack.sh file):

stack@http://Compute-node:/opt/stack/tempest⟫ tox -efull
full develop-inst-nodeps: /opt/stack/tempest
full installed: anyjson==0.3.3,Babel==2.0,boto==2.38.0,cffi==1.2.1,cliff==1.14.0,cmd2==0.6.8,cryptography==1.0,debtcollector==0.7.0,ecdsa==0.13,enum34==1.0.4,extras==0.0.3,fasteners==0.13.0,fixtures==1.3.1,functools32==3.2.3.post2,httplib2==0.9.1,idna==2.0,ipaddress==1.0.14,iso8601==0.1.10,jsonschema==2.5.1,linecache2==1.0.0,monotonic==0.3,msgpack-python==0.4.6,netaddr==0.7.15,netifaces==0.10.4,os-testr==0.3.0,oslo.concurrency==2.4.0,oslo.config==2.2.0,oslo.context==0.5.0,oslo.i18n==2.4.0,oslo.log==1.9.0,oslo.serialization==1.8.0,oslo.utils==2.3.0,paramiko==1.15.2,pbr==1.5.0,posix-ipc==1.0.0,prettytable==0.7.2,pyasn1==0.1.8,pycparser==2.14,pycrypto==2.6.1,pyOpenSSL==0.15.1,pyparsing==2.0.3,python-mimeparse==0.1.4,python-subunit==1.1.0,pytz==2015.4,PyYAML==3.11,retrying==1.3.3,six==1.9.0,stevedore==1.7.0,-e git+http://ift.tt/1Jl0rv2
full runtests: PYTHONHASHSEED='55362061'
full runtests: commands[0] | find . -type f -name *.pyc -delete
full runtests: commands[1] | bash tools/pretty_tox.sh (?!.*\[.*\bslow\b.*\])(^tempest\.(api|scenario|thirdparty)) 
running testr

Tempest stops here and do nothing more.

and in the log file:

2015-08-25 22:04:31.284 25801 DEBUG tempest.test [-] Add resource to test flavor generate_scenario tempest/test.py:652
2015-08-25 22:04:31.285 25801 DEBUG tempest.test [-] [('inv_res_flavor', {'expected_result': 404, 'resource': ('flavor', '7e0484e1-6374-426b-89c9-621d0249ea0a')})] generate_scenario tempest/test.py:662
2015-08-25 22:04:31.285 25801 DEBUG tempest.test [-] {'http-method': 'GET', 'json-schema': {'properties': {'minDisk': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}, 'minRam': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}}, 'type': 'object'}, 'url': 'flavors/detail', 'name': 'list-flavors-with-detail'} generate_scenario tempest/test.py:640
2015-08-25 22:04:31.286 25801 DEBUG tempest.test [-] [('minDisk_gen_none', {'_negtest_name': 'minDisk_gen_none', '_negtest_generator': <bound method NegativeTestGenerator.gen_none of <tempest.common.generator.negative_generator.NegativeTestGenerator object at 0x7f068cbaff50>>, '_negtest_schema': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}, '_negtest_path': ['minDisk']}), ('minDisk_gen_string', {'_negtest_name': 'minDisk_gen_string', '_negtest_generator': <bound method NegativeTestGenerator.gen_string of <tempest.common.generator.negative_generator.NegativeTestGenerator object at 0x7f068cbaff50>>, '_negtest_schema': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}, '_negtest_path': ['minDisk']}), ('minRam_gen_none', {'_negtest_name': 'minRam_gen_none', '_negtest_generator': <bound method NegativeTestGenerator.gen_none of <tempest.common.generator.negative_generator.NegativeTestGenerator object at 0x7f068cbaff50>>, '_negtest_schema': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}, '_negtest_path': ['minRam']}), ('minRam_gen_string', {'_negtest_name': 'minRam_gen_string', '_negtest_generator': <bound method NegativeTestGenerator.gen_string of <tempest.common.generator.negative_generator.NegativeTestGenerator object at 0x7f068cbaff50>>, '_negtest_schema': {'results': {'gen_string': 400, 'gen_none': 400}, 'type': 'integer'}, '_negtest_path': ['minRam']})] generate_scenario tempest/test.py:662

I do not know that Tempest is started or not? but I sure that no test was run.
Please help me to explain about that :|, do I need to do anything after rebooting server to make Tempest run normally? I don't know why. Please teach me to check and how to fix this issue.

Thank you very much for your help.

Aucun commentaire:

Enregistrer un commentaire