_allocate_vr_id not working as expected because of REPEATABLE READ transactions

Bug #1520152 reported by Cedric Brandily
10
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_ALLOCATION_TRIES):
   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.db.l3_hamode

Tags: db l3-ha
Changed in neutron:
status: New → Confirmed
importance: Undecided → High
Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Cedric Brandily (<email address hidden>) on branch: master
Review: https://review.openstack.org/250040

Revision history for this message
Cedric Brandily (cbrandily) wrote :
Changed in neutron:
status: In Progress → Fix Committed
Changed in neutron:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.