Bug 1125398

Summary: Prevent users from deleting an environment if it has content views or systems since doing so would bypass the dynflow code
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: Content ManagementAssignee: Partha Aji <paji>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: daviddavis, paji
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6815
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-14 11:42:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Helms 2014-07-31 18:13:10 UTC

Comment 1 Eric Helms 2014-07-31 18:13:11 UTC
Created from redmine issue http://projects.theforeman.org/issues/6815

Comment 2 Eric Helms 2014-07-31 18:13:13 UTC
Upstream bug assigned to daviddavis

Comment 4 David Davis 2014-08-06 21:21:10 UTC
Prevent a user from deleting an environment if it has systems or content views. Currently, if you deleted a content view, it removes its systems and content views by bypassing the dynflow code. We need to prevent that for 6.0.4.


The workaround (until we have lifecycle environment destroy dynflowed) is to remove the content views and reassign systems using the content view deletion page.

Comment 5 David Davis 2014-08-06 21:22:29 UTC
Here is the BZ to implement lifecycle environment destroy:

https://bugzilla.redhat.com/show_bug.cgi?id=1125358

Comment 6 David Davis 2014-08-14 11:42:31 UTC
We're dynflowizing environment delete so closing this out.