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:
Removing satellite packages using katello-remove appears to be very slow in comparison to what was there in 6.2 release.

For a comparison, I tried running katello-remove on both 6.2.11 and 6.3 Snap 16.0 and got the following results:

Katello-remove on 6.2.11

real	13m24.804s
user	7m50.206s
sys	1m44.923s

Katello-remove on 6.3 Snap 16.0

real	41m5.501s
user	31m25.616s
sys	1m37.319s

Going by these numbers, katello-remove seems to be atleast twice as slow in comparison to 6.2 releases.

Can something be done here?

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19941 has been resolved.

katello-remove has finished in < 3 minutes in Satellite 6.3 snap 28. Thus I am moving this to VERIFIED.

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336