DHCP port creation is asynchronous with subnet creation.
Therefore there is a time window where, depending on how fast
the DHCP agent honors the request, the DHCP port IP allocation
may or may not be accounted for in the total number of used IP
for the network. To kill the race, do not run dhcp on the
created subnets at all.
Reviewed: https:/ /review. openstack. org/299647 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=27634bb2ba2 637d694c7d0aa57 58173d12ef579a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 27634bb2ba2637d 694c7d0aa575817 3d12ef579a
Author: Armando Migliaccio <email address hidden>
Date: Wed Mar 30 14:24:58 2016 -0700
Fix race conditions in IP availability API tests
DHCP port creation is asynchronous with subnet creation.
Therefore there is a time window where, depending on how fast
the DHCP agent honors the request, the DHCP port IP allocation
may or may not be accounted for in the total number of used IP
for the network. To kill the race, do not run dhcp on the
created subnets at all.
Closes-bug: 1563883
Change-Id: Idda25e65d04852 d68a3c160cc9dee fdb4ee82dcd