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!