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:
If there is never a case where system templates from "Library" should be uploaded to Cloud Engine for building then the ability to download from Library should be removed. If a user would like to verify the template before promoting the UI should be sufficient for review. If the UI is not sufficient for reviewing then it should be made sufficient and the ability to download from "Library" should still be removed.

Couple options since there are some users that really like being able to view the raw template even in the library:

1) Big warning in an XML comment that this is a template from the Library and should not be used to provision systems with

2) Render it as text instead of XML so it is impossible to use outside the scope of just validation

3) Render it as XML but change the tags so it is not usable 

I've CLOSED:WONTFIX bugs like this a few times but we should be able to find some sort of compromise.

getting rid of 6.0.0 version since that doesn't exist

Closing old bugs which are not relevant based on new UI and CLI

Closing old bugs which are not relevant based on new UI and CLI