Red Hat Bugzilla – Bug 1465146
fetching list of applicable errata is slow with if lots of hosts need lots of errata
Last modified: 2018-02-07 13:48:34 EST
Description of problem:
If you have lots of hosts that need errata, fetching the "applicable" errata can be very slow.
Version-Release number of selected component (if applicable): 6.2.10
How reproducible: every time
Steps to Reproduce:
1. create lots of hosts that have applicable errata, or load up a database with this data
2. go to errata page
Actual results: waiting for minutes if either "applicable" or "installable" are checked
Expected results: page should load within 5-10 seconds
Created redmine issue http://projects.theforeman.org/issues/20167 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20167 has been resolved.
Created attachment 1314237 [details]
applying to 6.2.11:
download the patch to /tmp/
patch -p1 < /tmp/filename.patch
then restart httpd and foreman-tasks
Created attachment 1322818 [details]
Created attachment 1322819 [details]
=== HOTFIX INSTRUCTIONS FOR SATELLITE 6.2.11 ONLY ===
1. Download attached file bz1465146-hotfix-rpms-el7sat.tar.xz or bz1465146-hotfix-rpms-el6sat.tar.xz depending on your Satellite host OS version
2. Stop Satellite
3. Extract the tarball and install the packages
4. Start Satellite
Verified in Satellite 6.2.14 Snap 1.
Registered over 5300 content hosts to the satellite, each with 102 applicable errata. Repeated reloads of the errata page took no more than 9 seconds, including refresh time. Average page load time appears to be around 4-4.5 seconds.
See attached screenshot for load time confirmation.
Created attachment 1380829 [details]
verification screenshot 1
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.