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:
As part of multi capsule creation, created around 400 capsules on virtual machines. After creating capsules on,  Some of the VM''s had to be removed due to some storage issues.  Once VM image is undefine/deleted, tried to remove capsule from GUI. 

Fails to remove capsules with below error:

vmcapsule319.perf.lab.eng.rdu.redhat.com is used by vmcapsule319.perf.lab.eng.rdu.redhat.com



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

6.1 GA
RHEL 7.1 Satelitte/Capsule

How reproducible:


Steps to Reproduce:
1. create multi capsules on virtual machines and register with satelitte server
2. delete/destroy some VM's. try to remove capsule from GUI. 
3.

Actual results:

Capsule is not getting removed
Expected results:
Capsule should be removed

Additional info:

Note: I have observed that in order to delete the capsule, the user must first delete the host associated with it.

Per 6.3 planning, moving out non acked bugs to the backlog

Based on comment #1 from Brad that is the correct method. This is a sanity check to not cause FK in the postgres table. Once you delete the hosts then you can delete the capsule.

Closing this out

- Chris