Bug 1326354

Summary: satellite does not pull latest sat6tools pulp packages
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: PulpAssignee: Michael Hrivnak <mhrivnak>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, jsherril, lpramuk
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-14 12:15:47 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 sthirugn@redhat.com 2016-04-12 13:55:02 UTC 
Description of problem:
satellite does not pull latest sat6tools pulp packages

Version-Release number of selected component (if applicable):
satellite-6.2.0-7.0.beta.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Sync satellite6 tools from dogfood url and check the pulp packages
2. Compare the synced packages with the packages in the dogfood url


Actual results:
pulp-rpm-handlers-2.8.1.1-1.el7sat.noarch
python-pulp-common-2.8.1.2-1.el7sat.noarch
python-pulp-rpm-common-2.8.1.1-1.el7sat.noarch
python-pulp-agent-lib-2.8.1.2-1.el7sat.noarch

Expected results:
pulp-rpm-handlers-2.8.1-3.el7sat.noarch.rpm
python-pulp-common-2.8.1.3-1.el7sat.noarch.rpm
python-pulp-rpm-common-2.8.1-3.el7sat.noarch.rpm
python-pulp-agent-lib-2.8.1.3-1.el7sat.noarch.rpm


Additional info:
Comment 2 Justin Sherrill 2016-04-12 18:34:15 UTC 
we're 99% sure that this was an issue with the http proxy this server had been configured with.  The problem has gone away after 24 hours which lends itself to this.
Comment 3 sthirugn@redhat.com 2016-04-13 15:05:26 UTC 
Verified as per Comment 2.  The satellite boxes are working fine now.  I will fix proxy not to cache the dogfood url and monitor it.  If I see this issue again, I will reopen it.