[openstack-dev] swift & keystone failing in devstack
Michael Kerrin
michael.kerrin at hp.com
Tue Jun 25 07:50:49 UTC 2013
Hi there,
we raised a bug https://bugs.launchpad.net/devstack/+bug/1193112 where the
default configuration of swift in devstack interacts badly with keystone. We
end up with the following exception iwth swift-proxy-server:
$ cd /opt/stack/swift && /opt/stack/swift/bin/swift-proxy-server
/etc/swift/proxy-server.conf -v || touch "/opt/stack/status/stack/s-
proxy.failure"
proxy-server Starting keystone auth_token middleware
proxy-server Using /var/cache/swift as cache directory for signing certificate
proxy-server signing_dir mode is 0755 instead of 0700
proxy-server Starting the S3 Token Authentication component
Traceback (most recent call last):
File "/opt/stack/swift/bin/swift-proxy-server", line 22, in <module>
run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
File "/opt/stack/swift/swift/common/wsgi.py", line 249, in run_wsgi
loadapp(conf_path, global_conf={'log_name': log_name})
File "/opt/stack/swift/swift/common/wsgi.py", line 100, in wrapper
return f(conf_uri, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247,
in loadapp
return loadobj(APP, uri, name=name, **kw)
File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272,
in loadobj
return context.create()
File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710,
in create
return self.object_type.invoke(self)
File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 207,
in invoke
app = filter(app)
File "/opt/stack/keystone/keystone/middleware/s3_token.py", line 215, in
auth_filter
return S3Token(app, conf)
File "/opt/stack/keystone/keystone/middleware/s3_token.py", line 65, in
__init__
self.http_client_class = environment.httplib.HTTPConnection
AttributeError: 'NoneType' object has no attribute 'HTTPConnection'
I raised a work around here https://review.openstack.org/#/c/34207/ not in the
hope that this code will get committed but in the hope that someone will see
this and know what to do. That review is also a work around for anyone hit by
this bug.
So if anyone knows what to do for this bug please help,
Michael
More information about the OpenStack-dev
mailing list