Move db retry logic closer to where DB error occur
Bug #1612798 reported by
Armando Migliaccio
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Kevin Benton |
Bug Description
This has caused weird failure modes where DB errors get masked by integrity violation errors.
Changed in neutron: | |
status: | New → Confirmed |
assignee: | nobody → Kevin Benton (kevinbenton) |
importance: | Undecided → Low |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
importance: | Low → High |
Changed in neutron: | |
milestone: | none → newton-rc1 |
Changed in neutron: | |
assignee: | Kevin Benton (kevinbenton) → Armando Migliaccio (armando-migliaccio) |
Changed in neutron: | |
assignee: | Armando Migliaccio (armando-migliaccio) → Kevin Benton (kevinbenton) |
summary: |
- Move db retry logic away from API layer + Move db retry logic closer to where DB error occur |
To post a comment you must log in.
DB errors get masked by integrity violation errors or vice versa?