[openstack-dev] [QA]Bug in tempest/scenario/manager.py, wrong tenant being used for the selected admin user.
David Kranz
dkranz at redhat.com
Tue Sep 17 20:54:06 UTC 2013
On 09/17/2013 04:30 PM, Martinez, Castulo wrote:
>
> Hi Guys,
>
> I found what seems to be a bug in the tempest/scenario/manager.py
> module in Tempest.
>
> In the "credentials" classmethod definition for the
> "OrchestrationScenarioTest" class (Line 637),
>
> @classmethod
>
> *def* *credentials*(cls):
>
> username *=* cls*.*config*.*identity*.*admin_username
>
> password *=* cls*.*config*.*identity*.*admin_password
>
> tenant_name *=* cls*.*config*.*identity*.*tenant_name
>
> *return* username, tenant_name, password
>
> Looks like the following line:
>
> tenant_name *=* cls*.*config*.*identity*.*tenant_name
>
> Should be replaced by this one:
>
> tenant_name *=* cls*.*config*.*identity*.admin_*tenant_name
>
> Right now the script is trying to use the admin username and password
> with the wrong tenant name (a non admin one).
>
> Should I open a bug for this? If so, can somebody instruct me how to
> do this?
>
>
So the same appears in OrchestrationManager.__init__ and
OfficialClientManager._get_orchestration_client.
I'ts strange because I would expect tests to be failing. I have cc'ed
Steve Baker to see if he can shed light on this.
And you can file a tempest bug at this page:
https://bugs.launchpad.net/tempest/+filebug
-David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130917/72e22858/attachment.html>
More information about the OpenStack-dev
mailing list