Red Hat Bugzilla – Bug 1349120
heat stack-delete not removing floating ip and subsequently failing
Last modified: 2016-12-14 10:41:15 EST
Description of problem: Discovered while running a tripleo-ci ping test script on top of a newton deployment, which consists of an overcloud populated by a heat stack (which created an instance, floatingips, router...). The heat stack-delete failed on Newton each time. [1] By digging into the heat engine and neutron server logs, we can see that heat asks to delete the floatingips and then router interface directly after[2]. But if you look at the neutron server log [3], it shows that the request for deleting the floating is done few seconds after. The remove_router_interface occurred at 14:12:52.594 and the request for the deleting the floating ip at 2016-06-22 14:12:54.510 How reproducible: Easily Steps to Reproduce: 1. Deploy OpenStack (Newton) with TripleO 2. ssh into the undercloud as the stack user 3. Execute a pingtest/validate the overcloud[4] - creating a `tenant-stack` on the overcloud for testing and then attempting to delete it during cleanup 4. $ source overcloudrc 5. $ openstack stack list Actual results: +--------------------------------------+--------------+---------------+---------------------+---------------------+ | id | stack_name | stack_status | creation_time | updated_time | +--------------------------------------+--------------+---------------+---------------------+---------------------+ | 96d21224-f532-457f-be6f-e04d836a2b05 | tenant-stack | DELETE_FAILED | 2016-06-22T13:39:38 | 2016-06-22T13:41:11 | +--------------------------------------+--------------+---------------+---------------------+---------------------+ Expected results: +--------------------------------------+--------------+---------------+---------------------+---------------------+ | id | stack_name | stack_status | creation_time | updated_time | +--------------------------------------+--------------+---------------+---------------------+---------------------+ | 96d21224-f532-457f-be6f-e04d836a2b05 | tenant-stack | UPDATE_COMPLETE | 2016-06-22T13:39:38 | 2016-06-22T13:41:11 | +--------------------------------------+--------------+---------------+---------------------+---------------------+ Additional info: [1] - https://paste.fedoraproject.org/383244/66039931/ [2] - https://paste.fedoraproject.org/383279/66072051/ [3] - https://paste.fedoraproject.org/383325/10212146/ [4] - https://paste.fedoraproject.org/383404/61838514/
The fix for this has landed upstream
Steve, can you please help moving the bug to modified with version of package this is in?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html