Bug 928558

Summary:	add support for Swift cache in authtoken m/w
Product:	Red Hat OpenStack	Reporter:	Alan Pevec <apevec>
Component:	python-keystoneclient	Assignee:	Alan Pevec <apevec>
Status:	CLOSED ERRATA	QA Contact:	Pavel Sedlák <psedlak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0 (Folsom)	CC:	ayoung, cpelland, mpavlase, psedlak, sclewis, ykaul
Target Milestone:	snapshot2
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-keystoneclient-0.2.3-1.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-12 16:43:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alan Pevec 2013-03-27 23:00:46 UTC

Description of problem:
https://bugs.launchpad.net/keystone/+bug/1020127/comments/14
"you *must* set this option (cache=swift.cache) if you are using auth_token in a swift proxy server."

Requires backport of https://github.com/openstack/python-keystoneclient/commit/62be31419f3a8765407ad583110fc7d36fb64dcf

Comment 6 Pavel Sedlák 2013-06-06 18:15:14 UTC

Verified with python-keystoneclient-0.2.3-2.el6ost.
When cache = swift.cache is set in filter:authtoken section of swift/proxy-server.conf, authtoken m/w in proxy-server reports that it will use memcache from swift.cache.

Settings just memcache_servers (direct memcached for authtoke, instead of inheriting it from swift) does not works as parsing of that option fails, but should be caused by different change and so was moved to bug #971497.

Comment 7 Alan Pevec 2013-06-07 17:24:19 UTC

(In reply to Pavel Sedlák from comment #6)
> Settings just memcache_servers (direct memcached for authtoke, instead of
> inheriting it from swift) does not works as parsing of that option fails,

Direct memcached probably doesn't make sense within Swift, so that's not critical, but we can discuss that in the cloned bug 971497.

Comment 9 errata-xmlrpc 2013-06-12 16:43:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0944.html