[openstack-dev] [heat] heat delete woes in Juno
matt at mattfischer.com
Fri Mar 27 20:05:00 UTC 2015
Here is a link to one of the stacks. It is fairly simple just some
routers/nets/subnets. The description is a bit odd perhaps, but legal. I've
changed the template to not point at IPs at internal DNS.
I created and deleted this in a loop about 5 times and it finally failed to
delete on the last run. Now that it is stuck in DELETE_FAILED no amount of
deleting will help. I'm concerned that a template this simple can get stuck
I will have stack_abandon enabled next week as it just landed in Puppet:
https://review.openstack.org/#/c/168157/ and will plan on trying that then.
On Thu, Mar 26, 2015 at 12:40 PM, Pavlo Shchelokovskyy <
pshchelokovskyy at mirantis.com> wrote:
> Hi Matt,
> if it would be feasible/appropriate, could you provide us with templates
> for stacks that show this behavior (try to get them with "heat
> template-show <stack-name-or-id>")? This would help us to test and
> understand the problem better.
> And yes, just the day before I was contacted by one of my colleagues who
> seems to experience similar problems with Juno-based OpenStack deployment
> (though I did not had a chance to look through the issue yet).
> Best regards,
> Pavlo Shchelokovskyy
> Software Engineer
> Mirantis Inc
> On Thu, Mar 26, 2015 at 8:17 PM, Matt Fischer <matt at mattfischer.com>
>> Nobody on the operators list had any ideas on this, so re-posting here.
>> We've been having some issues with heat delete-stack in Juno. The issues
>> generally fall into three categories:
>> 1) it takes multiple calls to heat to delete a stack. Presumably due
>> to heat being unable to figure out the ordering on deletion and resources
>> being in use.
>> 2) undeleteable stacks. Stacks that refuse to delete, get stuck in
>> DELETE_FAILED state. In this case, they show up in stack-list and
>> stack-show, yet resource-list and stack-delete deny their existence. This
>> means I can't be sure whether they have any real resources very easily.
>> 3) As a corollary to item 1, stacks for which heat can never unwind the
>> dependencies and stay in DELETE_IN_PROGRESS forever.
>> Does anyone have any work-arounds for these or recommendations on
>> cleanup? My main worry is removing a stack from the database that is still
>> consuming the customer's resources. I also don't just want to remove stacks
>> from the database and leave orphaned records in the DB.
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev