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:
Running yum repolist on a system that was just registered against a Katello or SAM returns a 404.
Version-Release number of selected component (if applicable):
* katello-0.1.211-2.el6.noarch
* candlepin-0.5.15-1.el6.noarch
* pulp-0.0.263-1.el6.noarch
How reproducible:
Steps to Reproduce:
1. Follow these steps to register a client: https://fedorahosted.org/katello/wiki/GuideSystemRegistrationClient
2. In the client run yum repolist
3.
Actual results:
yum repolist
Loaded plugins: product-id, subscription-manager
Updating Red Hat repositories.
https://qetello02.usersys.redhat.com/pulp/repos/NY_Data_Center/Development/custom/System_Engine/Stable/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Trying other mirror.
Expected results:
Additional info:
Turns out the 8080 just masked the error a bit. 8080 is the tomcat connector port and yum errored out trying to connect, generating a non-obvious error during update.
Closing as NOTABUG and filing new bugs WRT any 404s received during yum operations.