DB2 deadlock error not detected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
High
|
Unassigned | ||
Glance |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned | ||
OpenStack Heat |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned | ||
neutron |
Invalid
|
Undecided
|
Unassigned | ||
oslo-incubator |
Fix Released
|
Undecided
|
Bryan Jones |
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:/
but for DB2
This is an example error:
2014-07-01 19:52:16.574 2710 TRACE nova.openstack.
Changed in nova: | |
status: | New → Confirmed |
tags: | added: db oslo |
summary: |
- DB2 deadlock error not supported + DB2 deadlock error not detected |
Changed in neutron: | |
status: | New → Confirmed |
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → High |
description: | updated |
Changed in oslo: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
importance: | Undecided → Low |
Changed in keystone: | |
status: | New → Invalid |
Changed in nova: | |
status: | Confirmed → Invalid |
Fix proposed to branch: master /review. openstack. org/106458
Review: https:/