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.
Bug 1419126 - activation key page takes 10-20 seconds to load for each batch of keys
Summary: activation key page takes 10-20 seconds to load for each batch of keys
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.2.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-03 16:13 UTC by Chris Duryee
Modified: 2022-03-13 14:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
verification screenshot 1 (133.39 KB, image/png)
2018-01-29 18:55 UTC, jcallaha
no flags Details
verification screenshot 2 (133.39 KB, image/png)
2018-01-29 18:56 UTC, jcallaha
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20584 0 None None None 2017-08-14 12:42:30 UTC

Description Chris Duryee 2017-02-03 16:13:39 UTC
Description of problem:

If you go to the activation key page (content -> activation keys), it can take a long time for the page to load. It looks like two calls to candlepin are made for each key, each taking about 300msec.

Ideally, the number of calls to candlepin would not scale linearly with the number of activation keys.

If the activation key page could load each "page" of data in under 5 seconds, that would be much better.

Version-Release number of selected component (if applicable): 6.2.7


Steps to Reproduce:
1. create 20 or 30 activation keys
2. view AK page

Actual results: slow load time. I got 18 seconds locally but I've seen up to 45 seconds.


Expected results: 5 second load time or better

Comment 4 Brad Buckingham 2017-08-14 12:42:29 UTC
Created redmine issue http://projects.theforeman.org/issues/20584 from this bug

Comment 5 Satellite Program 2017-08-17 18:15:37 UTC
Upstream bug assigned to paji

Comment 8 Satellite Program 2017-09-25 14:15:31 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20584 has been resolved.

Comment 9 Justin Sherrill 2017-11-27 15:18:16 UTC
Proposed for 6.3.0 since it is fixed upstream

Comment 11 jcallaha 2018-01-29 18:52:59 UTC
Verified in Satellite 6.3 Snap 33.

The page load times have been reduced significantly. See below averages as well as the attached screenshots.

Load from other pages: 1.8s - 6.5s
Reload: 7s
Switching between paginated AK loads: 0.5 - 1.5s

Comment 12 jcallaha 2018-01-29 18:55:48 UTC
Created attachment 1387951 [details]
verification screenshot 1

Comment 13 jcallaha 2018-01-29 18:56:30 UTC
Created attachment 1387952 [details]
verification screenshot 2

Comment 14 Satellite Program 2018-02-21 16:54:37 UTC
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


Note You need to log in before you can comment on or make changes to this bug.