Hi Steve,
The initial implementation of environment deletion (before 'destroy' method
was introduced in MuranoPL) was to deploy environment with empty
application list. So the code that deletes Heat stack was in 'deploy'. And
it is still there. Environment's 'destroy' will be executed only in case
Object Model is empty (doesn't contain Environment object), not in the case
it is present, but application list is empty. Now if you say that stack
doesn't get deleted it is clearly a bug that need to be filled in
launchpad. I'm not sure why it can happen. Maybe API behavior was changed
recently to send empty Object Model or it sends incorrect action name. This
just need to be debugged.
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Wed, Jun 25, 2014 at 3:57 AM, McLellan, Steven
wrote:
> Is there any reason the system Environment class doesn’t implement
> destroy? Without it, the pieces of the heat stack not owned by other
> resources get left lying around. It looks like it was once implemented as
> part of deploy, but that no longer seems to execute.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
