the application destroy() method should be executed prior to release any resources

Bug #1630488 reported by Artem Akulshin on 2016-10-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Wishlist
Unassigned

Bug Description

The problem reported here https://bugs.launchpad.net/murano/+bug/1629804 would never occur if default behaviour was to execute destroy() or other muranopl method before releasing any resources in application to give ability to execute muranopl code before releasing any resources. The usecase for that can be releasing DNS record, windows domain record or any other external system registration like CM or whatever.

Changed in murano:
status: New → Confirmed
importance: Undecided → Wishlist
milestone: none → ocata-1
Changed in murano:
milestone: 3.1.0 → pike-2
Changed in murano:
milestone: pike-2 → pike-rc1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers