yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1340793

Title:
  DB2 deadlock error not detected

Status in Cinder:
  Confirmed
Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in Orchestration API (Heat):
  New
Status in OpenStack Identity (Keystone):
  Invalid
Status in OpenStack Neutron (virtual network service):
  Confirmed
Status in OpenStack Compute (Nova):
  Confirmed
Status in The Oslo library incubator:
  Fix Released

Bug description:
  Currently, only mysql and postgresql deadlock errors are properly handled.
  The error message for DB2 looks like:

  'SQL0911N  The current transaction has been rolled back because of a
  deadlock or timeout.  <deadlock details>'

  Olso.db needs to include a regex to detect this deadlock. Essentially the same as
      https://bugs.launchpad.net/nova/+bug/1270725
  but for DB2

  This is an example error:

  2014-07-01 19:52:16.574 2710 TRACE
  nova.openstack.common.db.sqlalchemy.session ProgrammingError:
  (ProgrammingError) ibm_db_dbi::ProgrammingError: Statement Execute
  Failed: [IBM][CLI Driver][DB2/LINUXX8664] SQL0911N  The current
  transaction has been rolled back because of a deadlock or timeout.
  Reason code "2".  SQLSTATE=40001 SQLCODE=-911 'UPDATE reservations SET
  updated_at=updated_at, deleted_at=?, deleted=id WHERE
  reservations.deleted = ? AND reservations.uuid IN (?, ?, ?)'
  (datetime.datetime(2014, 7, 1, 23, 52, 10, 774722), 0,
  'e2353f5e-f444-4a94-b7bf-f877402c15ab', 'c4b22c95-284a-4ce3-810b-
  5d9bbe6dd7b7', 'ab0294cb-c317-4594-9b19-911589228aa5')

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