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.

Workaround:

1.  Create a new lifecycle environment
2.  Promote some content view (with at least one repo) to it
3.  Take your capsule and remove all lifecycle environments, assign it to the new one in 1)
4.  Sync the capsule. 
5.  When the sync is complete, re-assign the capsule to the lifecycle environments you care about.
6.  Remove the content view version from the lifecycle environment you created in 1) and then delete the lifecycle environment

Note this will be solved by the same fix as https://bugzilla.redhat.com/show_bug.cgi?id=1418747

Based on Comment 3, I am closing this out as current release as it should be been fixed as of 6.2.8. If you are still seeing this after 6.2.8 please feel free to re-open.