Bug 1326354 - satellite does not pull latest sat6tools pulp packages
Summary: satellite does not pull latest sat6tools pulp packages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Michael Hrivnak
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 13:55 UTC by sthirugn@redhat.com
Modified: 2019-04-01 20:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-14 12:15:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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