Activity log for bug #1340793

Date Who What changed Old value New value Message
2014-07-11 15:05:19 Bryan Jones bug added bug
2014-07-11 15:06:37 Bryan Jones bug task added nova
2014-07-11 18:26:12 OpenStack Infra oslo: status New In Progress
2014-07-11 18:26:12 OpenStack Infra oslo: assignee Bryan Jones (jonesbr)
2014-07-11 19:35:11 Matt Riedemann nova: status New Confirmed
2014-07-11 19:35:15 Matt Riedemann tags db oslo
2014-07-11 19:39:05 Matt Riedemann bug task added keystone
2014-07-11 19:39:22 Matt Riedemann bug task added cinder
2014-07-11 19:39:33 Matt Riedemann bug task added heat
2014-07-11 19:39:52 Matt Riedemann bug task added glance
2014-07-11 19:40:11 Matt Riedemann bug task added neutron
2014-07-11 19:40:28 Matt Riedemann summary DB2 deadlock error not supported DB2 deadlock error not detected
2014-07-12 08:07:24 Eugene Nikanorov neutron: status New Confirmed
2014-07-14 19:04:51 Jay Bryant cinder: status New Confirmed
2014-07-14 19:05:08 Jay Bryant cinder: importance Undecided High
2014-07-17 11:32:27 OpenStack Infra oslo: status In Progress Fix Committed
2014-07-26 19:14:17 Matt Riedemann 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 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')
2014-07-29 07:58:30 Thierry Carrez oslo: status Fix Committed Fix Released
2014-07-29 07:58:30 Thierry Carrez oslo: milestone juno-2
2014-09-12 22:33:12 Sean Dague nova: importance Undecided Low
2014-09-23 18:56:00 Morgan Fainberg keystone: status New Invalid
2014-10-24 13:51:53 Viktor Serhieiev glance: status New Invalid
2014-10-24 13:52:52 Viktor Serhieiev heat: status New Invalid
2015-03-17 17:20:32 Michal Dulko cinder: status Confirmed Invalid
2015-08-02 23:23:07 Davanum Srinivas (DIMS) nova: status Confirmed Invalid
2015-11-09 12:34:16 Ihar Hrachyshka neutron: status Confirmed Invalid