Bug 820774 - mysql by default fails to rollback to savepoints on ppc64
Summary: mysql by default fails to rollback to savepoints on ppc64
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Beaker
Classification: Retired
Component: inventory
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard: MC
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-10 23:36 UTC by Nish Aravamudan
Modified: 2012-11-07 07:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-07 07:22:26 UTC
Embargoed:

Attachments (Terms of Use)

Description Nish Aravamudan 2012-05-10 23:36:21 UTC 
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 07:22:26 UTC 
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.