← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1520152] [NEW] _allocate_vr_id not working as expected because of REPEATABLE READ transactions

 

Public bug reported:

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

** Affects: neutron
     Importance: Undecided
     Assignee: Cedric Brandily (cbrandily)
         Status: New


** Tags: db l3-ha

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1520152

Title:
  _allocate_vr_id not working as expected because of REPEATABLE READ
  transactions

Status in neutron:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1520152/+subscriptions


Follow ups