Issues running keystone swift with no S3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If we follow the instructions on this page :
http://
and use the non S3 config (in swift-proxy.conf) with the simple pipeline :
[pipeline:main]
pipeline = catch_errors healthcheck cache tokenauth keystone proxy-server
we can't authenticate using the simple curl command we use to use :
curl -k -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' https:/
we get a 401 response and no connection from swift to keystone.
If we enable the S3 stuff, it looks like swift is requesting /s3tokens instead of /v2.0/s3tokens and we get this error :
2012-03-15 14:28:54 DEBUG [routes.middleware] No route matched for POST /s3tokens
[DEFAULT]
bind_port = 8080
bind_ip = 0.0.0.0
user = swift
cert_file = /etc/swift/
key_file = /etc/swift/
log_name = swift
log_facility = LOG_LOCAL1
log_level = DEBUG
workers = 1
[pipeline:main]
# broken but in doc
# pipeline = cache tokenauth keystone proxy-server
# working
pipeline = cache swift3 s3token tokenauth keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_
account_autocreate = true
[filter:swift3]
use = egg:swift#swift3
log_facility = LOG_LOCAL1
[filter:keystone]
paste.filter_
operator_roles = Member, admin
[filter:s3token]
paste.filter_
service_port = 5000
service_host = 192.168.240.19
auth_port = 35357
auth_host = 192.168.240.19
auth_protocol = http
auth_token = ADMIN
admin_token = ADMIN
[filter:tokenauth]
paste.filter_
service_port = 5000
service_host = 192.168.240.19
auth_port = 35357
auth_host = 192.168.240.19
auth_protocol = http
auth_token = ADMIN
admin_token =ADMIN
admin_tenant_name = service
admin_user = swift
admin_password = secrete
cache = swift.cache
as noted in the documentation you need to auth against keystone not swift itself a very rough shell script available here would show to do that: http:// p.chmouel. com/ks