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.

This is a RFE to provide a mechanism, to quickly see if a system conforms to specification or not. Make sure RPMs & config files are as expected or not. For RPM you could build release rpms that hold the certified software including versions as requirements. That way you'll see quickly if the systems complies or not. This would also help to prevent unwanted software changes on this system. The config file compliance could probably been checked when puppet gets integrated. In larger customer environments this is a vital feature to keep the environment manageable over time. With this i can easily determine my one-offs. And fix them.

You could do this with puppet today. Since there are no templates any longer in Satellite 6.0, I am going to close this out. If you disagree with this please feel free to re-open.