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:


Doing a :

hammer capsule synchronize 

will happily sync your capsule even if nothing is attached to sync.  It should throw an error if there is nothing to sync explaining that lifecycle environments need to be attached.

Created redmine issue http://projects.theforeman.org/issues/6673 from this bug

Proposed fix in Katello PR: 
   https://github.com/Katello/katello/pull/4489

Based on feedback on the PR in comment #3, we did not merge the proposed changes.  It appears that there is a valid use case for performing a sync on a capsule that has no lifecycle environments attached.  For example, it would help to clear a capsule if for some reason the server didn't automatically initiate the cleanup when the lifecycle environments are removed.

For this BZ, it might be useful to return a 'warning' to the user; however, given that we do not do anything like that today for other APIs, we are going to move this bug to a future release.

I am closing this based on usptream discussions at https://github.com/Katello/katello/pull/4489. If you disagree, please reopen with your reasoning.