On Mon, Apr 15, 2019 at 4:39 PM Rabi Mishra <ramishra at redhat.com> wrote: > I think this had been discussed on several occasions before and one of the > suggestions from the neutron team was to use compare-and-swap update api  > to avoid race conditions. > >  http://lists.openstack.org/pipermail/openstack-dev/2018-June/131020.html >  https://bugs.launchpad.net/neutron/+bug/1703234 Thank you for your quick answer. I did read that previous discussion and I did not properly understand why compare-and-swap was recommended. To my understanding compare-and-swap allows a client to detect a race with another, but it would not eliminate the races. All clients would have to retry until success and with the current OS::Neutron::ExtraRoute we do actively generate those races. That's why I went in the directions mentioned in my original mail. Am I missing something?