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, a Content View version can only be removed if it is promoted to an environment.

This is not intuitive and does not follow the natural workflow.

When creating a new Content View version it is automatically promoted to the Library environment, thereby replacing the previous version. Further promotions do again oust the previous version, leaving the old version unused eventually.

These unused old versions pile up and can only be removed by promoting them to Library again one by one.

Given the requirement of being unused before removing, the necessity of promotion before removing is even dangerous since exactly this makes the old version available again...

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

The restriction described no longer exists.  In Satellite 6.2 (and 6.1), it is possible to remove a content view version that is not currently associated with a Lifecycle Environment.  

Closing this bugzilla; however, please re-open this one or create a new one, if issues additional issues are identified.  Thanks!