Thanks for traceback. I reported a bug on launchpad[1] based on your logs.
Below you can find several possible solutions at the moment:
1) Wait for bug-fix
2) Create neutron subnet manually(some tutorials: [2], [3])
3) Copy existing Tempest configuration file into Rally(Rally stores Tempest
config
Thanks Andrey! Please see below the logs(Environment specific output has
been snipped):
2014-06-04 02:32:07.303 1939 DEBUG rally.cmd.cliutils [-] INFO logs from
urllib3 and requests module are hide. run
/usr/local/lib/python2.7/dist-packages/rally/cmd/cliutils.py:137
2014-06-04 02:32:07.363 1939 I
Hey, Om!
Can you launch Rally in debug mode and share logs?
> rally -vd verify start --set image
On Tue, Jun 3, 2014 at 3:49 PM, om prakash pandey
wrote:
> Hi Andrey,
>
> Thanks a ton for putting together this blog on using tempest + rally.
>
> I followed all the steps listed and managed to get
Hi Andrey,
Thanks a ton for putting together this blog on using tempest + rally.
I followed all the steps listed and managed to get tempest successfully
installed.
However, I was not able to proceed beyond and couldn't manage to run
tempest even once. I am getting the below error:
om@desktop2:~
Hi stackers,
I would like to share with you great news.
We all know that it's quite hard to use Tempest out of gates, especially
when you are going to benchmark different clouds, run just part of tests
and would like to store somewhere results. As all this stuff doesn't belong
to Tempest, we decid