Back to bug 1042163

Who When What Removed Added
RHOS Integration 2013-12-12 21:14:55 UTC Keywords FutureFeature
Whiteboard upstream_milestone_icehouse-2 upstream_status_implemented
Red Hat Bugzilla 2013-12-12 21:14:55 UTC Doc Type Bug Fix Enhancement
John Skeoch 2014-01-13 01:15:46 UTC CC hateya
Stephen Gordon 2014-01-23 20:51:08 UTC Status NEW POST
RHOS Integration 2014-02-19 22:25:05 UTC Whiteboard upstream_milestone_icehouse-2 upstream_status_implemented upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
RHOS Integration 2014-02-20 16:02:13 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 17:21:41 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 17:53:50 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 18:24:11 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 21:47:52 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 22:17:52 UTC Target Release --- 5.0
Scott Lewis 2014-03-26 18:41:38 UTC CC sbaker, sdake, shardy
Component RFEs openstack-heat
Steven Dake 2014-04-08 16:57:16 UTC Priority unspecified low
Doc Text Feature:
Delete a stack without deleting the resources.

Reason:
A user may wish to delete the stack from the Heat database without actually removing the stack resource instantations.

Result (if any):
When using this functionality, the stack resources remain after a stack deletion occurs.
Scott Lewis 2014-07-07 13:41:46 UTC Target Milestone Upstream M2 rc
Scott Lewis 2014-07-07 13:53:16 UTC Target Milestone rc ga
Scott Lewis 2014-07-22 19:09:00 UTC Status POST CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-07-22 15:09:00 UTC
Martin Lopes 2014-07-23 04:18:11 UTC CC mlopes
Doc Text Feature:
Delete a stack without deleting the resources.

Reason:
A user may wish to delete the stack from the Heat database without actually removing the stack resource instantations.

Result (if any):
When using this functionality, the stack resources remain after a stack deletion occurs.
With this enhancement, users are able to abandon a stack in Orchestration and still retain the stack resources.
As a result, stack resources remain after a stack abandon operation.

Back to bug 1042163