ostf tests does double deletion of two ips in test_008_check_public_instance_connectivity_from_instance test

{"release": "4.0", "nailgun_sha": "dc49dd346ab303269018355e825581139bd6b873", "ostf_sha": "c1c353909cd1a0af018bbe89fb12570db6b09969", "astute_sha": "75aa0877cba772f409d3cef4f36ba2ec1b8b603b", "fuellib_sha": "2d9ae05f9a08e51bdabdca9baaab6e6941e8cb79"}
Deployment mode: nova-network, centos, flatdhcp

I see this in logs after tests run:
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: 172.16.0.2 "DELETE /v2/46f4516b6fbd461eb30f17409
36c2167/os-floating-ips/1 HTTP/1.1" status: 202 len: 209 time: 0.0797279
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: (19517) accepted ('172.16.0.2', 47613)
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: 172.16.0.2 "DELETE /v2/46f4516b6fbd461eb30f17409
36c2167/os-floating-ips/1 HTTP/1.1" status: 202 len: 209 time: 0.0804379
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: (19517) accepted ('172.16.0.2', 47615)
<0>Dec 19 17:52:08 node-2 <BF><180>nova-nova.db.sqlalchemy.api WARNING: Change will make usage less than 0 for the fol
lowing resources: ['floating_ips']
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: 172.16.0.2 "DELETE /v2/46f4516b6fbd461eb30f17409
36c2167/os-floating-ips/2 HTTP/1.1" status: 202 len: 209 time: 0.0822539
<182>Dec 19 17:52:08 node-2 nova-nova.osapi_compute.wsgi.server INFO: (19517) accepted ('172.16.0.2', 47617)
<0>Dec 19 17:52:09 node-2 <BF><180>nova-nova.db.sqlalchemy.api WARNING: Change will make usage less than 0 for the fol
lowing resources: ['floating_ips']
<182>Dec 19 17:52:09 node-2 nova-nova.osapi_compute.wsgi.server INFO: 172.16.0.2 "DELETE /v2/46f4516b6fbd461eb30f17409
36c2167/os-floating-ips/2 HTTP/1.1" status: 202 len: 209 time: 0.0815802

Expected behavior:
one removal of one floating ip.

I've tried to allocate floating from console client and it creates only one DELETE request.

Looks like there is another bug in nova-network that corrupts counters. As I understand, nobody in OpenStack cares about nova-network, so I'm not going to report a bug.