_allocate_vr_id not working as expected because of REPEATABLE READ transactions
Bug #1520152 reported by
Cedric Brandily
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Cedric Brandily |
Bug Description
The method _allocate_vr_id[1] uses the pattern:
for count in range(MAX_
try:
<select some candidates using a DB query>
<try to allocate a candidate>
return candidate
except DBDuplicateEntry:
pass
Because of REPEATABLE READ transactions, the selected candidate is always the same, so if first try fails then next tries will also fail.
[1] neutron.
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Change abandoned by Cedric Brandily (<email address hidden>) on branch: master /review. openstack. org/250040
Review: https:/