Bug 1009148

Summary: Repository pages are very slow and/or unresponsive
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: WebUIAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: mmccune
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-17 20:18:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Corey Welton 2013-09-17 19:17:16 UTC
Description of problem:
Attempting to access the repo pages in build is very slow, if it responds at all

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


How reproducible:


Steps to Reproduce:
1.  Install build on fresh box.  Upload known good manifest
2.  Attempt to access Custom repositories page; view results
3.  Attempt to access Red Hat Repositories page; view results

Actual results:
* Custom repos page eventually loads but gets a perpetual spinner in the left pane.
* Red Hat Repositories page never seems to load (waited ~5 minutes)

Note that viewing any other page is responsive enough.


Expected results:
Pages load and provide appropriate content.

Additional info:

Comment 1 Corey Welton 2013-09-17 19:20:15 UTC
Satellite-6.0.2-RHEL-6-20130913.1

Comment 2 Corey Welton 2013-09-17 19:22:38 UTC
Not seeing anything out of the ordinary in the katello production.log, checking elsewhere.

Comment 4 Corey Welton 2013-09-17 19:39:25 UTC
Possible false alarm.  The RH repos page did finally load, after a very, very long time.  Will leave this here for investigation but removing blocker.

Comment 5 Mike McCune 2013-09-17 20:18:48 UTC

*** This bug has been marked as a duplicate of bug 1008636 ***