When you load an old version of keystoneclient doing legacy tests and
then start the test app the ec2 work that depends on keystoneclient sees
the recently loaded legacy one which doesn't have the required modules
in it.
If we load the app first the ec2 modules are resolved and finds the
original keystone client. The ec2 module then uses
'from keystoneclient.contrib.ec2 import utils as ec2_utils' so the
ec2_utils reference is kept in the file scope so isn't affected by the
tests changing keystoneclient.
It is not a long term fix for bug 1178532 but it solves the immediate
symptoms when running client tests independently.
Reviewed: https:/ /review. openstack. org/36395 github. com/openstack/ keystone/ commit/ 2aaa902d6eb16fe 9ee2e7bc262c1b2 9731c03a0c
Committed: http://
Submitter: Jenkins
Branch: master
commit 2aaa902d6eb16fe 9ee2e7bc262c1b2 9731c03a0c
Author: Jamie Lennox <email address hidden>
Date: Wed Jul 10 16:45:18 2013 +1000
Load app before loading legacy client in tests.
When you load an old version of keystoneclient doing legacy tests and
then start the test app the ec2 work that depends on keystoneclient sees
the recently loaded legacy one which doesn't have the required modules
in it.
If we load the app first the ec2 modules are resolved and finds the contrib. ec2 import utils as ec2_utils' so the
original keystone client. The ec2 module then uses
'from keystoneclient.
ec2_utils reference is kept in the file scope so isn't affected by the
tests changing keystoneclient.
It is not a long term fix for bug 1178532 but it solves the immediate
symptoms when running client tests independently.
Change-Id: I7267ca0d4740f0 37884fae95f8a65 62ee86584b9