Back to bug 1377518
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-09-20 01:34:02 UTC | Target Release | --- | 10.0 (Newton) |
| Ajay Kalambur | 2016-09-20 01:37:21 UTC | Target Release | 10.0 (Newton) | 8.0 (Liberty) |
| Red Hat Bugzilla Rules Engine | 2016-09-20 01:37:25 UTC | Target Release | 8.0 (Liberty) | 10.0 (Newton) |
| Chandra Ganguly | 2016-09-20 01:45:18 UTC | CC | ganguly | |
| Whiteboard | hot | |||
| Assaf Muller | 2016-09-20 02:12:41 UTC | Status | NEW | ASSIGNED |
| Target Release | 10.0 (Newton) | 8.0 (Liberty) | ||
| Assignee | amuller | hmlnarik | ||
| Assaf Muller | 2016-09-20 02:13:50 UTC | Priority | unspecified | high |
| Target Milestone | --- | async | ||
| RHEL Program Management | 2016-09-20 04:04:55 UTC | Keywords | ZStream | |
| Charles Crouch | 2016-09-20 16:40:08 UTC | CC | charcrou | |
| Charles Crouch | 2016-09-20 16:40:33 UTC | Blocks | 1194008 | |
| Faiaz Ahmed | 2016-09-20 23:00:22 UTC | CC | fahmed | |
| Faiaz Ahmed | 2016-09-21 00:11:11 UTC | CC | hmlnarik | |
| Flags | needinfo?(hmlnarik) | |||
| Hynek Mlnarik | 2016-09-21 07:52:26 UTC | Link ID | OpenStack gerrit 373102 | |
| Flags | needinfo?(hmlnarik) | |||
| Hynek Mlnarik | 2016-09-21 07:52:47 UTC | Link ID | OpenStack gerrit 361681 | |
| Hynek Mlnarik | 2016-09-21 07:53:05 UTC | Link ID | OpenStack gerrit 361679 | |
| Hynek Mlnarik | 2016-09-21 07:53:24 UTC | Link ID | OpenStack gerrit 373031 | |
| Hynek Mlnarik | 2016-09-21 14:05:33 UTC | Blocks | 1378123 | |
| Hynek Mlnarik | 2016-09-21 14:39:11 UTC | Status | ASSIGNED | POST |
| Hynek Mlnarik | 2016-09-23 14:00:25 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-neutron-7.1.1-7.el7ost | |||
| Hynek Mlnarik | 2016-09-26 07:02:33 UTC | Doc Text | Cause: Due to concurrency, db error by precommit is sometimes inevitable. precommit may issue db transactions depending on mechanism driver, Some operations on e.g. subnet, routers, touches many other resources (e.g. ip allocation, ports) in single db transaction as well. And background operation by mechanism driver (e.g. background sync, monitoring resources periodically, etc) may touch those db tables with other order. Consequence: Transaction sometimes fails in precommit phase. Fix: Retry on fail. Result: Mitigation of the precommit issues. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| errata-xmlrpc | 2016-09-29 18:04:42 UTC | Status | MODIFIED | ON_QA |
| Toni Freger | 2016-10-06 11:37:05 UTC | Status | ON_QA | VERIFIED |
| Martin Lopes | 2016-10-10 05:15:57 UTC | CC | mlopes | |
| Doc Text | Cause: Due to concurrency, db error by precommit is sometimes inevitable. precommit may issue db transactions depending on mechanism driver, Some operations on e.g. subnet, routers, touches many other resources (e.g. ip allocation, ports) in single db transaction as well. And background operation by mechanism driver (e.g. background sync, monitoring resources periodically, etc) may touch those db tables with other order. Consequence: Transaction sometimes fails in precommit phase. Fix: Retry on fail. Result: Mitigation of the precommit issues. | Database precommit errors are sometimes inevitable due to the nature of concurrency. Precommit may issue database transactions depending on the mechanism driver, for example, certain operations on subnets and routers may interact with many other resources in a single database transaction (for example, IP allocation, ports). In addition, background operations for mechanism drivers (for example, background sync, monitoring resources periodically, among others) may touch those database tables with other requests. As a result of this behavior, transactions may sometimes fail during the precommit phase. With this update, the transaction will retry on failure, resulting in the mitigation of precommit issues. |
||
| errata-xmlrpc | 2016-10-11 14:28:08 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-10-11 15:12:10 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-10-11 11:12:10 UTC |
Back to bug 1377518