Found possible root cause: list_ranges_by_allocation_pool had locking parameter, but it was not used in code. So IpamAvailabilityRange was not locked during transaction.
Fix is https://review.openstack.org/223123 Need to test it with IPAM Driver Enabled, i.e make https://review.openstack.org/#/c/181023/ depend on this fix and verify no more failures observed in gate-neutron-dsvm-api
Found possible root cause: by_allocation_ pool had locking parameter, but it was not used in code. yRange was not locked during transaction.
list_ranges_
So IpamAvailabilit
Fix is https:/ /review. openstack. org/223123 /review. openstack. org/#/c/ 181023/ depend on this fix and verify no more failures observed in gate-neutron- dsvm-api
Need to test it with IPAM Driver Enabled, i.e make https:/