yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #17218
[Bug 1340793] Re: DB2 deadlock error not supported
** Changed in: nova
Status: New => Confirmed
** Tags added: db oslo
** Also affects: keystone
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Also affects: heat
Importance: Undecided
Status: New
** Also affects: glance
Importance: Undecided
Status: New
** Also affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- DB2 deadlock error not supported
+ DB2 deadlock error not detected
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1340793
Title:
DB2 deadlock error not detected
Status in Cinder:
New
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in Orchestration API (Heat):
New
Status in OpenStack Identity (Keystone):
New
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
Confirmed
Status in Oslo - a Library of Common OpenStack Code:
In Progress
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1340793/+subscriptions
References