Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1136171
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh109 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
Migrated Products
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1136171
-
When Keystone AuthToken m/w is used in Swift proxy server it fails to use memcache_servers option
Summary:
When Keystone AuthToken m/w is used in Swift proxy server it fails to use mem...
Keywords
:
Documentation
Status
:
CLOSED CURRENTRELEASE
Alias:
None
Product:
Red Hat OpenStack
Classification:
Red Hat
Component:
doc-Release_Notes
Sub Component:
---
Version:
5.0 (RHEL 7)
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
unspecified
Target Milestone:
---
Target Release
:
5.0 (RHEL 7)
Assignee:
Don Domingo
QA Contact:
RHOS Documentation Team
Docs Contact:
URL:
Whiteboard:
Depends On:
971497
Blocks:
TreeView+
depends on
/
blocked
Reported:
2014-09-02 05:43 UTC by
Don Domingo
Modified:
2016-04-27 03:29 UTC (
History
)
CC List:
9 users
(
show
)
ajeain
apevec
ayoung
dallan
dpal
jruzicka
psedlak
srevivo
yeylon
Fixed In Version:
Doc Type:
Known Issue
Doc Text:
When using Keystoneclient authtoken middleware with Swift, the option to use memcached directly doesn't work. For example, the following won't work: [filter:authtoken] memcache_servers = 127.0.0.1:11211 Instead, for token caching within Swift, authtoken middleware must be configured to use Swift's cache: cache=swift.cache
Clone Of:
971497
Environment:
Last Closed:
2015-03-10 03:35:57 UTC
Target Upstream Version:
Embargoed:
Attachments
(Terms of Use)
Note
You need to
log in
before you can comment on or make changes to this bug.