Glance lazy loading issue -- still coupled with Swift

[Matt Dietz]

When using glance without swift installed, an exception is thrown:

Traceback (most recent call last):
  File "/usr/local/lib/python2.6/dist-packages/eventlet/wsgi.py", line 347, in handle_one_response
    for data in result:
  File "/root/code/glance/trunk/glance/server.py", line 158, in image_iterator
    options=self.options)
  File "/root/code/glance/trunk/glance/store/__init__.py", line 80, in get_from_backend
    backend_class = get_backend_class(scheme)
  File "/root/code/glance/trunk/glance/store/__init__.py", line 58, in get_backend_class
    from glance.store.swift import SwiftBackend
  File "/root/code/glance/trunk/glance/store/swift.py", line 25, in <module>
    from swift.common.client import Connection, ClientException
ImportError: No module named swift.common.client

[Jay Pipes (jaypipes)]

is this a case of just needing from __future__ import absolute_import at the top of glance.store.__init__.py?

[Jay Pipes (jaypipes)]

Still not working. Latest trunk, run_tests.sh -V:

======================================================================
ERROR: Failure: ImportError (No module named swift.common.client)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jpipes/repos/glance/image-format/.glance-venv/lib/python2.6/site-packages/nose/loader.py", line 390, in loadTestsFromName
    addr.filename, addr.module)
  File "/home/jpipes/repos/glance/image-format/.glance-venv/lib/python2.6/site-packages/nose/importer.py", line 39, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/home/jpipes/repos/glance/image-format/.glance-venv/lib/python2.6/site-packages/nose/importer.py", line 86, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/home/jpipes/repos/glance/image-format/tests/unit/test_swift_store.py", line 28, in <module>
    import swift.common.client
ImportError: No module named swift.common.client

----------------------------------------------------------------------
Ran 74 tests in 5.654s

FAILED (errors=2)

Was swift removed from the pip-requires file?

[Rick Harris (rconradharris)]

> Was swift removed from the pip-requires file?

Not that I'm aware of.

Per Cory's comments, that looks like an 'acceptable' failure. The idea being, Swift isn't needed for a production deploy (so all of the actual code must use lazy loading). But, for developers, Swift is required to run the unit-tests to prevent integration/regression bugs.

[Jay Pipes (jaypipes)]

The tools/pip-requires file is *specifically* for developers that are running unit tests in a virtualenv. Therefore, Swift should be in the pip-requires file. So, no, it's not an acceptable failure.

[Jay Pipes (jaypipes)]

Note: it would be an acceptable failure if I had ./run_tests.sh -N. But I didn't. I ran it in run_tests.sh -V -f

[Rick Harris (rconradharris)]

Gotcha, never use venv; disregard.