Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Currently, we disable capsules during the clone by disabling tftp,dhcp and dns and disassociating them from LCEs.
When using the clone tool for testing purposes (e.g. during Beta testing), it can be useful to completely remove all capsules so that the testing clone isn't at risk of communication with production capsules due to unexpected behavior or human error.
Satellite doesn't support force deleting of capsules, so validations will prevent deleting a capsule on a cloned machine. There isn't a ton we can do about that in satellite-clone without causing issues elsewhere. Currently, to remove a capsule, you must remove any associations that will prevent it from being deleted.
Here are some steps that others have found helpful (some steps may not apply to your environment):
- for remote execution, go to administer->settings->remote execution and ensure that `remote_execution_without_proxy` is set to No/False
- then for every subnet, on the remote execution tab remove all capsules, and also on the capsules tab set all the dropdowns to empty
- for all domains set the dns capsule to empty
- for puppet/puppetca - on hosts page, select all hosts, choose all hosts not only on this page, and from the dropdown choose "change puppetmaster" and set it to none, and the same for puppet ca
After this, you should be able to delete a capsule.
If you run into trouble with these steps or still can't delete a capsule on a clone, please comment and we can debug further.
At this time, there are no additional code changes planned; therefore, I am going to close the bugzilla. If there are any concerns, please feel free to re-open with additional details.
The referenced KCS is intended to provide the steps the user may perform to enable them to remove the capsule.