Comment 0 for bug 1428434

I am using heat to boot some instances and create a new network , subnet and floatingip using neutron.

But when I delete this stack, I got this error:

2015-03-02 11:23:19.558 INFO heat.engine.resource [-] DELETE: RouterInterface "routerinterface" [c
d123476-962e-4d11-945b-773928a44905:subnet_id=1b43a9f5-d45f-4b43-995e-7c3625b06e81] Stack "wps_sta
ck" [1e63d62f-c397-4304-a53c-159d2532b5d3]
2015-03-02 11:23:19.558 TRACE heat.engine.resource Traceback (most recent call last):
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/resource.py
", line 466, in _action_recorder
2015-03-02 11:23:19.558 TRACE heat.engine.resource yield
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/resource.py", line 887, in delete
2015-03-02 11:23:19.558 TRACE heat.engine.resource
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/scheduler.py", line 295, in wrapper
2015-03-02 11:23:19.558 TRACE heat.engine.resource step = next(subtask)
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/resource.py", line 508, in action_handler_task
2015-03-02 11:23:19.558 TRACE heat.engine.resource yield
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/resources/neutron/router.py", line 361, in handle_delete
2015-03-02 11:23:19.558 TRACE heat.engine.resource self.client_plugin().ignore_not_found(ex)
2015-03-02 11:23:19.558 TRACE heat.engine.resource File "/opt/stack/heat/heat/engine/clients/client_plugin.py", line 132, in ignore_not_found
2015-03-02 11:23:19.558 TRACE heat.engine.resource raise ex
2015-03-02 11:23:19.558 TRACE heat.engine.resource Conflict: Router interface for subnet 1b43a9f5-d45f-4b43-995e-7c3625b06e81 on router cd123476-962e-4d11-945b-773928a44905 cannot be deleted, as it is required by one or more floating IPs.

This error does not happen every time when deleting the same stack, and when it happened if running 'stack-delete' command again, the stack can be deleted successfully.

I am not sure this is the same bug with #1418878.