On 03/12/2013 05:26 PM, Girija Sharan wrote:
Hi,
Thanks again.
I am getting this error whenever I
ran *tempest-stable-folsom/tempest/tests/network tests.
======================================================================
ERROR: test suite for <class
'tempest.tests.network.test_networks.NetworksTest'>
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 208, in run
self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 291, in
setUp
self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 314, in
setupContext
try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 478, in
try_run
return func()
File
"/home/controller/tempest-stable-folsom/tempest/tests/network/test_networks.py",
line 28, in setUpClass
super(NetworksTest, cls).setUpClass()
File
"/home/controller/tempest-stable-folsom/tempest/tests/network/base.py", line
39, in setUpClass
client.list_networks()
File
"/home/controller/tempest-stable-folsom/tempest/services/network/json/network_client.py",
line 13, in list_networks
resp, body = self.get('networks')
File
"/home/controller/tempest-stable-folsom/tempest/common/rest_client.py", line
166, in get
return self.request('GET', url, headers)
File
"/home/controller/tempest-stable-folsom/tempest/common/rest_client.py", line
203, in request
raise exceptions.NotFound(resp_body)
NotFound: Object not found
Details: Object not found
Details: 404 Not Found
The resource could not be found.
-------------------- >> begin captured logging << --------------------
tempest.config: INFO: Using tempest config file
/home/controller/tempest-stable-folsom/etc/tempest.conf
tempest.common.rest_client: ERROR: Request URL:
http://192.168.2.170:9696/v2.0/tenants/09b32430cf8548ec8472d29a79fe2ddd/networks
tempest.common.rest_client: ERROR: Request Body: None
tempest.common.rest_client: ERROR: Response Headers: {'date': 'Tue, 12
Mar 2013 11:47:32 GMT', 'status': '404', 'content-length': '52',
'content-type': 'text/plain; charset=UTF-8'}
tempest.common.rest_client: ERROR: Response Body: 404 Not Found
The resource could not be found.
--------------------- >> end captured logging << ---------------------
----------------------------------------------------------------------
Ran 0 tests in 0.186s
FAILED (errors=1)
Please help me out.
Thanks and Regards,
Girija Sharan Singh
On Tue, Mar 12, 2013 at 8:50 PM, Jay Pipes <[email protected]
<mailto:[email protected]>> wrote:
On 03/12/2013 11:14 AM, Girija Sharan wrote:
> But the tests in *tempest-stable-folsom/tempest/tests/network
*are not
> running in Folsom with Quantum. All other tests are running fine.
> Someone said that this stable-folsom release of tempest is not for
> testing Quantum in Folsom.
> Is it true ? If yes then how do I test my Quantum in Folsom
deployment
> using Tempest ?
Regarding your question about tempest.conf, in order to work with Folsom
OpenStack, you just need to make sure you have 2 non-admin users and
tenants, 2 active images, then copy the etc/tempest.conf.sample to
etc/tempest.conf and change the following:
uri
username, password, tenant_name
alt_username, alt_password, alt_tenant_name
admin_username, admin_password
image_ref, image_ref_alt
It will work for most of the tests.
If you're working with Quantum, catalog_type under "[network]" section
should be set to "network", for nova-network you should *probably* set
it to "compute".
Regarding the Quantum support in tempest - I'm not familiar with that
(at least not yet, anyone else can help here?) but if you would like to
perform the same operation in nova-network, networks list currently
won't work since the JSON/XML clients (that should call to "os-networks"
API entry point as described in http://api.openstack.org/api-ref.html)
are not implemented - they return 404 page too, but in case it's
implemented - I think the result you get in the above exception can also
indicate that the tenant you refers to does not exist and should be
configured in tempest.conf.
I'm sorry, I don't know how to answer your question without seeing the
errors you are getting when running Tempest.
-jay
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Thanks,
Rami Vaknin, QE @ Red Hat, TLV, IL.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
