yahoo-eng-team team mailing list archive

[Brant Knudson <bknudson@xxxxxxxxxx>]

I'm not able to recreate this anymore, so closing.

** Changed in: keystone
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1190657

Title:
  keystoneclient 1.1 and Essex tests fail when run by themselves

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  
  Running the keystoneclient tests by themselves fail. The Kc11TestCase tests and KcEssex3TestCase tests all fail. This makes testing difficult.

  To recreate, check out keystone and
  ./run_tests.sh test_keystoneclient

  Here's the stack trace with the boring parts removed:

  Traceback (most recent call last):                                       
    File "/opt/stack/keystone/tests/test_keystoneclient.py", line 46, in setUp
      self.public_server = self.serveapp('keystone', name='main')             
  ...
    File "/opt/stack/keystone/.venv/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 22, in import_string
      return pkg_resources.EntryPoint.parse("x=" + s).load(False)
    File "/opt/stack/keystone/.venv/local/lib/python2.7/site-packages/pkg_resources.py", line 2060, in load
      entry = __import__(self.module_name, globals(),globals(), ['__name__'])
    File "/opt/stack/keystone/keystone/service.py", line 24, in <module>
      from keystone.contrib import ec2
    File "/opt/stack/keystone/keystone/contrib/ec2/__init__.py", line 18, in <module>
      from keystone.contrib.ec2.core import *
    File "/opt/stack/keystone/keystone/contrib/ec2/core.py", line 39, in <module>
      from keystoneclient.contrib.ec2 import utils as ec2_utils
  ImportError: No module named contrib.ec2

  Note that there's a vendor/python-keystoneclient-
  master/keystoneclient/contrib/ec2/ but vendor/python-
  keystoneclient-0.1.1/keystoneclient/contrib/ec2 and vendor/python-
  keystoneclient-essex-3/keystoneclient/contrib/ec2 do not exist.

  When running all the tests, the keystoneclient 1.1 and Essex3 tests
  don't fail. Probably because something else has already imported the
  parts from a different keystoneclient.

  Tests should be able to run by themselves and shouldn't require
  running other tests first.

  This indicates that if you have keystoneclient 1.1 on your system then
  you won't be able to run a current keystone.

  So I think the fix is that when we start up the keystone server in the
  tests we should be using the master/system keystoneclient and not the
  vendor one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1190657/+subscriptions