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.
The issue occurs when making repeated large queries against the API service. The cache for the Pulpcore API access policy holds references to entire instances of views.
The caching mechanism for the Pulpcore API access policy was introduced in Pulpcore 3.20 and the first Satellite release in which it appears is Satellite 6.13.0
I created this BZ as a spin-off from from 2122872 to avoid overloading that BZ, which was originally created for a Satellite version that did not have this issue, and already tracks fixes in other components (satellite-installer, via puppet-pulpcore)
I am not sure about what everyone else feels about handling this scenario via new BZ but even if we are tracking this just for the lru_cache fix, the BZ should be having Version set to 6.13.2 or 6.13.3 but not 6.14.0 ..
This was an issue reported on 6.13 only by >= 4 customers for sure.
And perhaps those cases should be identified from the other BZ and attached here as well.
Created attachment 1982843[details]
RHEL 8 Hotfix RPM for Satellite 6.13.3
A hotfix RPM is now available for Satellite 6.13.3 on RHEL 8.
Installation instructions:
1. Take a backup or snapshot of the Satellite server.
2. Download the hotfix RPM python39-pulpcore-3.21.9-2.HOTFIXRHBZ2229788.el8pc.noarch.rpm from the attachment.
3. # dnf install ./python39-pulpcore-3.21.9-2.HOTFIXRHBZ2229788.el8pc.noarch.rpm --disableplugin=foreman-protector
4. # satellite-maintain service restart
Verified.
Version Tested: Satellite 6.14.0 Snap 12.0
Verification Steps:
1. Enable few large repos and sync all at once.
2. Monitor memory usage by pulpcore gunicorn process.
Result:
1. The spike in memory usage comes down once the syncing of repos get completed.
2. The caching has been removed from pulpcore.
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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818