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.

6.6 added a new feature to enable task cleanup with this RFE:

https://bugzilla.redhat.com/show_bug.cgi?id=1692425

this only effects new installations of Satellite 6 but users who upgraded from 6.5 and prior still find the cleanup disabled, verified via answer file on a 6.6 Satellite that I upgraded from 6.5:

# rpm -q satellite
satellite-6.6.0-7.el7sat.noarch

# grep automatic_cleanup /etc/foreman-installer/scenarios.d/satellite-answers.yaml 
  automatic_cleanup: false

We thought that this was specifically disabled so that customers who would not be surprised by automatic task cleanup happening. Has the view on this changed?

Looking at https://gitlab.sat.engineering.redhat.com/satellite6/satellite-installer/merge_requests/59 and https://bugzilla.redhat.com/show_bug.cgi?id=1737488 we did want to have it enabled by default.

Mike could we get a final say on what we specifically wanted?

yes, we want all new installs as well as all upgraded systems to have this on-by-default.

At this point, this is still the default to turn on automatic_cleanup for all new installations but not to affect prior installations. Given there have been a few releases where this is the case I am opting to close this.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days