"Too many connections" with MySQL + sql token driver + v3 auth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Dolph Mathews |
Bug Description
Reported on the mailing list by Miller, Mark M:
https:/
Excerpt:
(keystone.
Traceback (most recent call last):
File "/usr/local/
self.
...
File "/usr/lib/
super(
OperationalError: (OperationalError) (1040, 'Too many connections') None None
(access): ... INFO ... "POST http://
(eventlet.
tags: | added: grizzly-rc-potential |
Changed in keystone: | |
importance: | Undecided → High |
summary: |
- "Too many connections" with PKI + MySQL + "Too many connections" with MySQL |
Changed in keystone: | |
assignee: | nobody → Dolph Mathews (dolph) |
status: | Confirmed → In Progress |
no longer affects: | keystone/grizzly |
Changed in keystone: | |
milestone: | none → grizzly-rc3 |
Changed in keystone: | |
milestone: | grizzly-rc3 → 2013.1 |
Attempted to reproduce this with PKI + sqlite against v2 does not appear to reproduce the issue. However, switching to v3 (as indicated by the above backtrace) revealed a slightly different symptom, documented in bug 1162857. These two bugs may share the same underlying cause.