Public bug reported: A concurrent thread/server can use an IP allocation before the port creation that attempts to insert it on the local server gets a chance to commit its transaction to the database. So even though we have a dup check, it may return that the IP is not in use right before something else steals it.
http://logs.openstack.org/38/257938/9/gate/gate-neutron-dsvm- api/d98d247/logs/screen-q-svc.txt.gz?level=ERROR ** Affects: neutron Importance: High Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) ** Changed in: neutron Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1534447 Title: ip allocation can be taken after dup check before commit Status in neutron: New Bug description: A concurrent thread/server can use an IP allocation before the port creation that attempts to insert it on the local server gets a chance to commit its transaction to the database. So even though we have a dup check, it may return that the IP is not in use right before something else steals it. http://logs.openstack.org/38/257938/9/gate/gate-neutron-dsvm- api/d98d247/logs/screen-q-svc.txt.gz?level=ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1534447/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
