On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it... we'll start running it in Jenkins. But so far I've heard from
the
On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it... we'll start running it in Jenkins. But so far I've heard from
the
There is still a bug in tempest and/or keystone. To run Tempest and
devstack you have to:
1. Add catalog_name=compute to tempest.conf
2. Change name to type in rest_client.py
-David
On 2/27/2012 8:18 AM, Ionuț Arțăriși wrote:
On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:49
I'm actively looking into any issues. I have all these tests passing locally in
my environment, so the issues seem to be focused around people using devstack.
I've made some merge prop's that will take care of a few of the issues. One
issue that will certainly come up is that if you have rate
On 02/27/2012 05:13 PM, Daryl Walleck wrote:
I'm actively looking into any issues. I have all these tests passing locally in
my environment, so the issues seem to be focused around people using devstack.
I've made some merge prop's that will take care of a few of the issues. One
issue that
1. Add catalog_name=compute to tempest.conf
2. Change name to type in rest_client.py
Yep, easiest to just apply this patch:
git fetch https://review.openstack.org/p/openstack/tempest
refs/changes/59/4259/1 git format-patch -1 --stdout FETCH_HEAD
Cheers,
Eoghan
This isn't really a bug in either project, but a configuration issue. The name
of the endpoint isn't static, so making it 'nova' or 'compute' may not always
be correct. If you check the name of your Compute project that's returned in
the Keystone auth request, you can find the name and
On 2/27/2012 3:02 PM, Dean Troyer wrote:
On Mon, Feb 27, 2012 at 10:13 AM, Daryl Walleck
daryl.wall...@rackspace.com wrote:
I'm working on updating this document as I'm using Devstack so that I can
either smooth
over or enumerate issues that may come up when running the tests. If you run
There is currently a bug https://bugs.launchpad.net/tempest/+bug/933845
that will prevent tempest from working with keystone. That ticket
provides a workaround but still not all of the tests are working at the
moment. I think the goal is for tempest to become actively run but we
are not there
+daryl.walleck=rackspace@lists.launchpad.net] on behalf
of David Kranz [david.kr...@qrclab.com]
Sent: Wednesday, February 22, 2012 8:24 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] running Tempest continuously in the openstack project?
There is currently a bug https
Indeed, as soon as someone says I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it... we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite ready yet.
-Jim
David Kranz david.kr...@qrclab.com
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it... we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite
12 matches
Mail list logo
