Glance's auto-recovery of db connections is incompatible with newer sqlalchemy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
High
|
Adam Gandelman | ||
glance (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Commit https:/
glance -f index
service mysql restart
glance -f index
...results in the original Bug #954971 again. It appears, internally, sqlalchemy is now calling conn.execute() where it was calling session.execute(). The exceptions that now bubble up are those raised by the backend dialect in-use, and not SQLA proper.
I propose Glance re-instates the event listener for the catching this specific error, given:
- it works well
- its portable across both new and old versions of SQLA
- puts most of the work on the library for assuring consistent database connection over time
- has already been implemented across most other projects to fix this same issue
tags: | added: essex-rc-potential |
Changed in glance: | |
importance: | Undecided → High |
Changed in glance: | |
milestone: | none → essex-rc3 |
tags: | removed: essex-rc-potential |
Changed in glance (Ubuntu): | |
status: | New → Fix Released |
Changed in glance: | |
milestone: | essex-rc3 → 2012.1 |
Fix proposed to branch: master /review. openstack. org/5938
Review: https:/