Out of the box, tempest does not run cleanly, needs config file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Medium
|
Jay Pipes |
Bug Description
While trying to run tempest against a running devstack, I was just doing:
$> nosestests storm
Out of the box, with a fresh git clone, this causes a bunch of errors like this:
=======
ERROR: test suite for <class 'storm.
-------
Traceback (most recent call last):
File "/usr/lib/
self.setUp()
File "/usr/lib/
self.
File "/usr/lib/
try_
File "/usr/lib/
return func()
File "/home/
cls.os = openstack.Manager()
File "/home/
self.
File "/home/
auth_url, tenant_name)
File "/home/
auth_url)
File "/home/
resp, body = self.http_
File "/usr/lib/
(scheme, authority, request_uri, defrag_uri) = urlnorm(uri)
File "/usr/lib/
raise RelativeURIErro
RelativeURIError: Only absolute URIs are allowed. uri = 127.0.0.1
Unfortunately, the RelativeURIError is hiding the real error: that there is no etc/storm.conf file in the /tempest/storm directory. And since there is no way to specify the config file path to use in testing, the storm.config.
The solution is to modify the StormConfig and openstack.Manager classes to have a way of specifying a config file and also to raise a more appropriate error when a config file is not found or a default is incorrect.
Donald Ngo and myself both experienced this issue...
tags: | added: testcase |
tags: | added: compute |
tags: | removed: compute |
tags: | removed: testcase |
Changed in tempest: | |
status: | Fix Committed → Fix Released |
Changed in tempest: | |
milestone: | none → havana-3 |
https:/ /review. openstack. org/#change, 2050