{"push_id":560158358,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"809efb267e6971b5af1a429e96def4822bfea65b","before":"86b7cd098732e0a2c63fc9ee717bd6aa660be3e6","commits":[{"sha":"809efb267e6971b5af1a429e96def4822bfea65b","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Updated openstack/openstack\nProject: openstack/neutron  817ebe5da8b3216829d4d6b9c3a4547f570f6cd4\n\nDo not check twice IP allocations for auto-address subnets\n\nFor auto-address subnets such as those with SLAAC and DHCP_STATELESS\naddress modes it is ok to delete them even when there are active IP\nallocations.\n\nThe current logic might trigger unexpected 409 errors if IP\nallocations are made on these subnets concurrently with their\ndeletion.\n\nThis patch simply ensures the final check for active IP allocations is\nnot performed for this class of subnets; since all IP allocations will\nbe removed anyway, it does not make sense to check whether there are\nallocations at all. In fact, doing this check might cause a failure\nof the delete operation if an IP allocation is made concurrently.\n\nThis patch also factors out the logic for checking whether there are\nIP allocations on the subnet to avoid code duplication.\n\nCloses-Bug: #1414199\n\nChange-Id: I1c4ca6f677845f6e2e8d88f3629c0e91ca73b5d0","distinct":true,"url":"https://api.github.com/repos/openstack/openstack/commits/809efb267e6971b5af1a429e96def4822bfea65b"}]}