Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
From adding a new host all hosts provisioned from Satellite are managed by default. This should be an option to select on the Settings page to make all hosts unassociated when provisioning to avoid deleting VM's when removing profiles from the Satellite server.

Version-Release number of selected component (if applicable):
6.2.15

How reproducible:
every time

Steps to Reproduce:
1. Provision New VM
2. Delete the content host profile of the VM
3.

Actual results:
Deletes the Virtual Machine from the compute resource by default when removing profiles

Expected results:
Host's association will be set at provisioning time based on the setting.

Additional info:

Is there a reason why the user can't disassociate the VM before deleting it. The whole purpose of the compute resource is to allow the user the manage the VM on the compute provider. 

This RFE would seem to be counter to this.

After some discussion, I think it is appropriate to update the title/description of this BZ


When leveraging compute resources (which enable the user to manage not only the host, but the virtual machine itself), the consequences for deleting a system are a bit more grave. In a recent scenario, a user deleted > 100 VMs in this fashion. (by selecting them via the UI and selecting 'delete host') 

As such, a mechanism should be provided to the user to warn and/or prevent deletion of a system if that system is linked to a virtual machine on a compute resource.

could this be implemented as BZ 1549761 (global setting disabling the vm deletions) or do you want to have confirmation box?

*** This bug has been marked as a duplicate of bug 1549761 ***