Comment 7 for bug 814981

Finally had a chance to get this going again and correct the config problems, however, I now see this. If this warrants a new bug, I will gladly file. I'll post here first in case it is related to configuration upgrade issues.

2011-07-26 21:31:47 DEBUG [routes.middleware] Route path: '/images/:(id)', defaults: {'action': u'show', 'controller': <glance.common.wsgi.Resource object at 0x91bbf4c>}
2011-07-26 21:31:47 DEBUG [routes.middleware] Match dict: {'action': u'show', 'controller': <glance.common.wsgi.Resource object at 0x91bbf4c>, 'id': u'1'}
2011-07-26 21:31:47 DEBUG [eventlet.wsgi.server] Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.py", line 347, in handle_one_response
    for data in result:
  File "/usr/lib/pymodules/python2.7/glance/api/v1/images.py", line 194, in image_iterator
    options=self.options)
  File "/usr/lib/pymodules/python2.7/glance/store/__init__.py", line 79, in get_from_backend
    backend_class = get_backend_class(loc.store_name)
  File "/usr/lib/pymodules/python2.7/glance/store/__init__.py", line 72, in get_backend_class
    raise UnsupportedBackend("No backend found for '%s'" % backend)
UnsupportedBackend: No backend found for 'swift+https'
2011-07-26 21:31:47 DEBUG [eventlet.wsgi.server] 10.208.241.236 - - [26/Jul/2011 21:31:47] "GET /v1/images/1 HTTP/1.1" 200 0 0.020222

Attaching updated glance-api.conf and glance-registry.conf