Bug 688699

Summary: rubygem-sunspot consistently times out
Product: [Retired] Aeolus Reporter: Brian Harrington <bharrington>
Component: conductorAssignee: Ian McLeod <imcleod>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: kburres
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-25 22:48:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 684278    
Attachments:
Description Flags
Logs from attempting to install rubygem-sunspot none

Description Brian Harrington 2011-03-17 18:38:12 UTC 
Created attachment 486082 [details]
Logs from attempting to install rubygem-sunspot

Description of problem:
When attempting to install aeolus-conductor-daemons, the package rubygem-sunspot consistently times out from the repository.  All other packages download fine.

Version-Release number of selected component (if applicable):
http://repos.fedorapeople.org/repos/aeolus/packages/rhel-6/noarch/rubygem-sunspot-1.2.1-3.el6.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. yum install aeolus-conductor-daemons
2. wait 30 seconds.... fail
3. repeat
  
Additional info:

When attempting to curl down the file, it will wait an average of two minutes before starting the download.  Once it does, the download completes quickly.

If the timeout in /etc/yum.conf is changed to 300 seconds, the install will complete.  That being said, none of the rest of the packages have this issue.  I have completed the install 4 times in a row with the same issue.
Comment 1 wes hayutin 2011-03-22 13:01:41 UTC 
adding to ce-beta tracker
Comment 2 Brian Harrington 2011-03-25 22:48:38 UTC 
So after a bunch of troubleshooting I figured out what the problem was....

The client uses a commercial proxy vendor.  Due to the size of the package, it was downloading it to the proxy server & attempting to scan it for viruses.  There was something in this package that was taking much longer to process than all of the rest of the RPMs for Aeolus.  Thus, the timeouts became visible.  While this could be an issue in the gem, I am more apt to chalk it up to being an issue with the proxy server.