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:
Cannot delete compute resource because it was associated to RHEV VMs. It does not seems there is a way to remove that association without deleting VMs.

Version-Release number of selected component (if applicable):
Satellite 6.3/6.4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Delete compute resource will result delete associated VMs.


Expected results:
From cust's case comment:
The enhancement would go like this: Deleting a compute-engine should cascades and delete the association of host to the compute-engine. This should not required to be able to communicate with the compute engine.

Additional info:

Does this mean to keep the RHEV VM?
If so it's covered by: https://bugzilla.redhat.com/show_bug.cgi?id=1549761

I'm closing this as duplicate of 1549761, the BZ has been updated with the case.

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