Bug 1198774
| Summary: | some mysql "commands out of sync" errors may not be interpreted correctly as a "database disconnect" situation, sqlalchemy 0.8.4 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Michael Bayer <mbayer> |
| Component: | python-sqlalchemy | Assignee: | Michael Bayer <mbayer> |
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.0 (RHEL 6) | CC: | ajeain, apevec, lhh, nbarcet, sclewis, ssainkar, yeylon |
| Target Milestone: | z4 | Keywords: | ZStream |
| Target Release: | 5.0 (RHEL 6) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 0.8.4-2.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the MySQL-Python DBAPI was observed under some circumstances using the ProgrammingError exception class to report on the 'command out of sync' errors, which is considered to be the case where a connection need to be thrown away; the SQLAlchemy dialect only expected this error to be emitted within the OperationalError class. As a result, in some cases a MySQL-Python connection that became corrupt would not signal to the SQLAlchemy engine that the pool of connections should be disposed, leading the engine not being able to proceed with new operations.
With this update, the error handling scheme of the MySQL-Python dialect is modified to expect either the OperationalError or ProgrammingError exception class when testing for this particular class of error. As a result, the SQLAlchemy engine/connection pool now correctly disposes off its connections when a MySQL-Python ProgrammingError delivers the 'command out of sync' error code.
|
Story Points: | --- |
| Clone Of: | 1121798 | Environment: | |
| Last Closed: | 2015-04-16 14:38:19 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: | |||
| Bug Depends On: | 1121798 | ||
| Bug Blocks: | |||
|
Comment 5
Ami Jeain
2015-04-12 11:17:53 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. https://rhn.redhat.com/errata/RHBA-2015-0820.html |