Red Hat Bugzilla – Bug 1608597
Content Host Applicable Package List page can DOS Satellite
Last modified: 2018-08-22 16:07:18 EDT
1) Take large Satellite installation with 20,000 content hosts 2) Navigate to Content Host -> Pick a host with applicable Errata 3) Click Packages -> Applicable Packages 4) On large installations this page will never return (query takes 4h+ to complete). During execution of said query, Postgres will consume 20-40GB of disk swapping out the query results, consuming way more resources than it should and slowing overall operations of the Satellite.
Created attachment 1470560 [details] Proposed Patch 001
Upstream bug assigned to mmccune@redhat.com
You can test this even on a Satellite with ~1000-2000 Hosts with applicable errata. The page will take 30-40 seconds to load before this patch. With this update it will render quickly in under a second.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24389 has been resolved.
*** Satellite 6.3.2 Hotfix Instructions *** 1) download tfm-rubygem-katello-3.4.5.74-2.RHBZ1608597.tar from bug to Satellite server 2) untar archive 3) rpm -Uvh *.rpm 4) katello-service restart 5) resume operations
Created attachment 1470886 [details] tfm-rubygem-katello-3.4.5.74-2.RHBZ1608597.tar
Created attachment 1473222 [details] verification video Verified in Satellite 6.3.3 Snap 2. I setup over 4k content hosts, each with 376 applicable packages. Following the steps outlined in the initial report, I saw that that load times, of the applicable packages page, only took a couple of seconds. This is significantly lower than the 30s load times expected with only 1000 content hosts. See attached webm for verification
*** Bug 1614354 has been marked as a duplicate of this bug. ***
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/RHBA-2018:2550