This error seems to be happening more and more, especially in the dvr-multinode-full job.
The typical symptom is that the DHCP port allocation fails to get an IP, and it appears the subnet is getting deleted simultaneously with the request.
For example, here is the request on the server to allocate an IP for DHCP:
http://logs.openstack.org/14/356714/3/check/gate-tempest-dsvm-neutron-dvr-multinode-full/31d68fa/logs/screen-q-svc.txt.gz#_2016-08-19_03_01_02_267
But less than a second before that, the subnet was deleted due to the network being deleted:
http://logs.openstack.org/14/356714/3/check/gate-tempest-dsvm-neutron-dvr-multinode-full/31d68fa/logs/screen-q-svc.txt.gz#_2016-08-19_03_01_01_933
So that means this failure is the symptom of some other issue, such as why is tempest deleting this resource? We really need to figure this out...
This error seems to be happening more and more, especially in the dvr-multinode-full job.
The typical symptom is that the DHCP port allocation fails to get an IP, and it appears the subnet is getting deleted simultaneously with the request.
For example, here is the request on the server to allocate an IP for DHCP:
http:// logs.openstack. org/14/ 356714/ 3/check/ gate-tempest- dsvm-neutron- dvr-multinode- full/31d68fa/ logs/screen- q-svc.txt. gz#_2016- 08-19_03_ 01_02_267
But less than a second before that, the subnet was deleted due to the network being deleted:
http:// logs.openstack. org/14/ 356714/ 3/check/ gate-tempest- dsvm-neutron- dvr-multinode- full/31d68fa/ logs/screen- q-svc.txt. gz#_2016- 08-19_03_ 01_01_933
So that means this failure is the symptom of some other issue, such as why is tempest deleting this resource? We really need to figure this out...