Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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:

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.

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.