← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1608691] Re: exception translation for pymysql "Lock wait timeout exceeded" broken

 

Oslo.db fixes are here:
https://review.openstack.org/#/q/3277ef33f2a1f6a892f0832e2907acef7b45dc2b,n,z

** 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/1608691

Title:
  exception translation for pymysql "Lock wait timeout exceeded" broken

Status in neutron:
  In Progress
Status in oslo.db:
  Fix Released

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'}]

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1608691/+subscriptions