Legacy Swift auth blows up with service-header-mappings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Pete Zaitcev |
Bug Description
I had Swift with Keystone working. I updated Keystone with Essex-3 and this started happening:
[zaitcev@lembas ~]$ curl -v -H "X-Auth-User: admin" -H "X-Auth-Key: admpass" htt
p://kvm-
* About to connect() to kvm-rei port 5000 (#0)
* Trying fd2d:acfb:
* Trying 192.168.129.18... connected
* Connected to kvm-rei (192.168.129.18) port 5000 (#0)
> GET /v1.0 HTTP/1.1
> User-Agent: curl/7.21.7 (x86_64-
zlib/1.2.5 libidn/1.22 libssh2/1.2.7
> Host: kvm-rei:5000
> Accept: */*
> X-Auth-User: admin
> X-Auth-Key: admpass
>
< HTTP/1.1 500 Internal Server Error
< Content-Type: text/plain
< Content-Length: 655
< Date: Fri, 03 Feb 2012 05:17:06 GMT
< Connection: close
<
Traceback (most recent call last):
File "/usr/lib/
result = self.applicatio
File "/usr/lib/
return self.app(env, start_response)
File "/usr/lib/
json.
File "/usr/lib/
self.
KeyError: 'service-
* Closing connection #0
I understand we have a tokenauth that uses v2 directly, but for now I'd like just have something that works.
Changed in keystone: | |
milestone: | none → essex-4 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
assignee: | nobody → Pete Zaitcev (zaitcev) |
Changed in keystone: | |
milestone: | essex-4 → 2012.1 |
Actually never mind, the fix is trivial: just changing to ['service_ header_ mappings' ] /review. openstack. org/#change, 3742
https:/