Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Gutterball and the associated CLI:

# hammer content-report 

commands should be removed from Satellite as they are currently non-functional and the maintenance cost of including these 3 reports is not worth the short term benefit of their inclusion.

1) Ensure gutterball is removed upon upgrade 
2) Ensure new installs of Satellite 6.1+ do not include gutterball

Any plan to remove the associated gutterball database from postgresql??

(In reply to Stuart Auchterlonie from comment #4)
> Any plan to remove the associated gutterball database from postgresql??

Yes, the database will also be removed from postgresql

We are not going to do this in the 6.1 line and have this available in 6.2 and forward