Deleting floating ip failed when using nova-network

[Sergey Reshetnyak]

ENV:
Heat + nova-network, devstack

Steps to reproduce:
1. Create stack from template: http://paste.openstack.org/show/167973/
2. Try delete stack in cycle:
 $ while true; do heat stack-delete stack_name; done
3. After ~1min stack moved to DELETE_FAILED status
stack status: http://paste.openstack.org/show/167979/

[Kairat Kushaev (kkushaev)]

Sergey, could you please provide the flavor parameters and image name that you used during test?
I am trying to reproduce the error but haven't succeed with it.

[Kairat Kushaev (kkushaev)]

I managed to re-produce the issue.

[Steven Hardy (shardy)]

Can you clarify is the failure always happening on deletion of the NovaFloatingIpAssociation resource?

In theory the error path in handle_delete for the server, floating IP and association should all tolerate a previous (incomplete or in-progress delete), due to the self.client_plugin().ignore_not_found(e) path.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/154967

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/154967
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=c9ca48e7a008c21b76a0864334a4b0b2c475303d
Submitter: Jenkins
Branch: master

commit c9ca48e7a008c21b76a0864334a4b0b2c475303d
Author: kairat_kushaev <email address hidden>
Date: Wed Feb 11 18:03:09 2015 +0300

    Catch Conflict exc for floating ip association

    When heat is trying to delete floating ip association and nova
    can't find an association between floating ip and server
    nova raises conflict exception instead of not_found. It happens
    because nova assumes that request was incorrect (floating ip
    is existing but link is not actual).
    So heat need to support such kind of cases.

    Change-Id: I3cc1fb13b9d3f0c1a2f7ee1c8ae7a99160b28951
    Closes-bug: #1418878

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/160318

[Kairat Kushaev (kkushaev)]

Steven, sorry for late answer.
Nova generates conflict exception if there is no association between IP and server but server and ip address exist.
It consider it as non-actual request to the server data.