exception translation for pymysql "Lock wait timeout exceeded" broken

Bug #1608691 reported by Kevin Benton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Kevin Benton
oslo.db
Fix Released
High
Kevin Benton

Bug Description

It looks like the classifier for "lock wait timeout exceeded" as a DBDeadlock is not correct for pymysql. Snippet of traceback showing it as the generic DBError:

2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 120, in raise_mysql_exception
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource _check_mysql_exception(errinfo)
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 115, in _check_mysql_exception
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource raise InternalError(errno, errorvalue)
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource DBError: (pymysql.err.InternalError) (1205, u'Lock wait timeout exceeded; try restarting transaction') [SQL: u'SELECT ipavailabilityranges.allocation_pool_id AS ipavailabilityranges_allocation_pool_id, ipavailabilityranges.first_ip AS ipavailabilityranges_first_ip, ipavailabilityranges.last_ip AS ipavailabilityranges_last_ip \nFROM ipavailabilityranges INNER JOIN ipallocationpools ON ipallocationpools.id = ipavailabilityranges.allocation_pool_id \nWHERE ipallocationpools.subnet_id = %(subnet_id_1)s \n LIMIT %(param_1)s FOR UPDATE'] [parameters: {u'param_1': 1, u'subnet_id_1': u'344485c9-e600-40c0-8acf-d9ba98dacf99'}]

Changed in oslo.db:
assignee: nobody → Kevin Benton (kevinbenton)
Revision history for this message
Kevin Benton (kevinbenton) wrote :
Changed in neutron:
assignee: nobody → Kevin Benton (kevinbenton)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Kevin Benton (kevinbenton) wrote :

Fix for neutron will just be waiting for requirements bump

Changed in oslo.db:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/oslo.db 4.10.0

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

Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

We'll need to bump requirements in N as well as M where we see it happening (note the job failing is grenade, and the traceback is seen on the 'old' side of grenade).

Changed in oslo.db:
status: Confirmed → Fix Released
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Mitaka release request for oslo.db: https://review.openstack.org/352370

Changed in oslo.db:
status: Fix Released → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/353247

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
Kevin Benton (kevinbenton) wrote :
Changed in neutron:
status: In Progress → Fix Released
Changed in oslo.db:
status: In Progress → Fix Released
Changed in neutron:
status: Fix Released → In Progress
Revision history for this message
Akihiro Motoki (amotoki) wrote :

For reference, the fix in oslo.db master branch is https://review.openstack.org/#/c/349711/
and the backport to mitaka is https://review.openstack.org/350161

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Kevin Benton (<email address hidden>) on branch: master
Review: https://review.openstack.org/353247
Reason: merged in bot proposal here: https://review.openstack.org/#/c/354457/4

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/oslo.db 4.7.1

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

Changed in neutron:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.