Bug 820774 - mysql by default fails to rollback to savepoints on ppc64
mysql by default fails to rollback to savepoints on ppc64
Status: CLOSED INSUFFICIENT_DATA
Product: Beaker
Classification: Community
Component: inventory (Show other bugs)
0.9
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: Dan Callaghan
MC
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-10 19:36 EDT by Nish Aravamudan
Modified: 2012-11-07 02:22 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-07 02:22:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nish Aravamudan 2012-05-10 19:36:21 EDT
Starting from a fresh RHEL6.2 installation and working up to a full beaker-server, the mysql engine complains:

OperationalError: (OperationalError) (1305, 'SAVEPOINT sa_savepoint_1 does not exist') 'ROLLBACK TO SAVEPOINT sa_savepoint_1' ()

Adding "init_connect='SET autocommit=0'" to /etc/my.cnf and restarting MySQL fixes the issue locally. In theory, sqlalchemy should be handling this, though?
Comment 1 Min Shin 2012-11-07 02:22:26 EST
This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.

Note You need to log in before you can comment on or make changes to this bug.