| Summary: | Allow retry on DB error for precommit [osp-9] | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Hynek Mlnarik <hmlnarik> |
| Component: | openstack-neutron | Assignee: | Hynek Mlnarik <hmlnarik> |
| Status: | CLOSED ERRATA | QA Contact: | GenadiC <gcheresh> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 9.0 (Mitaka) | CC: | akalambu, amuller, chrisw, fahmed, ganguly, hmlnarik, mlopes, nyechiel, oblaut, srevivo, tfreger |
| Target Milestone: | async | Keywords: | Triaged, ZStream |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | hot | ||
| Fixed In Version: | openstack-neutron-8.1.2-6.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Due to the nature of concurrency, database precommit errors can occasionally occur. The precommit may issue database transactions, depending on the mechanism driver. Certain operations (for example, on subnets, routers) touch many other resources in a single database transaction (for example, IP allocation, ports). In addition, a background operation by the mechanism driver, (such as background sync, periodic resource monitoring) may touch those database tables in a different order.
Consequently, a transaction may sometimes fail in the precommit phase.
With this update, a retry is performed on the precommit failure. As a result, this can mitigate precommit issues.
|
Story Points: | --- |
| Clone Of: | 1377518 | Environment: | |
| Last Closed: | 2016-12-21 16:48:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1377518 | ||
| Bug Blocks: | |||
|
Comment 4
GenadiC
2016-11-24 10:06:53 UTC
This is not question for me but rather for your lead. Toni? Verified that the code is in the 9 version - openstack-neutron-8.1.2-12.el7ost.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2984.html |