yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #58345
[Bug 1630899] Re: mysql 1305 errores handled differently with Mysql-Python
** Changed in: oslo.db
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1630899
Title:
mysql 1305 errores handled differently with Mysql-Python
Status in neutron:
Confirmed
Status in oslo.db:
Fix Released
Bug description:
The following check https://review.openstack.org/#/c/326927/6/neutron/db/api.py , does not works when I am using:
MySQL-python (1.2.5)
oslo.db (4.13.3)
SQLAlchemy (1.1.0)
2016-10-06 04:39:20.674 16262 ERROR neutron.api.v2.resource OperationalError: (_mysql_exceptions.OperationalError) (1305, 'SAVEPOINT sa_savepoint_1 does not exist') [SQL: u'ROLLBACK TO SAVEPOINT sa_savepoint_1']
2016-10-06 04:39:20.674 16262 ERROR neutron.api.v2.resource
In the log and not catches by the is_retriable , because it fails on the _is_nested_instance(e, db_exc.DBError) check. The exception's type is: <class 'sqlalchemy.exc.OperationalError'>
.
I did not used the '+pymysql', so it is the old MySQL-python driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1630899/+subscriptions
References