mysql 1305 errores handled differently with Mysql-Python

[Attila Fazekas]

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

^^^ Is in the log.

Not caught 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.

[Roman Podoliaka (rpodolyaka)]

Apparently, it's not only this specific error, but others as well: they are currently raised as OperationalError's instead of InternalError's, which breaks oslo.db unit tests on mysql-python.

[Roman Podoliaka (rpodolyaka)]

Will be fixed in https://review.openstack.org/#/c/393315/

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/oslo.db 4.13.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/oslo.db 4.15.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/oslo.db 4.13.4 release.