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.
DescriptionAndrew Schofield
2014-07-24 21:17:29 UTC
Description of problem:
Enabling redhat repositories does not give a visual error that the repos cannot be contacted.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Premature save there!
We run Satellite 6 behind a proxy server. If the proxy servers are not configure then Content -> Red Hat Repositories and trying to view a repository set (to enable a repo) does not give a visual clue (the wheel just continually spins whilst trying to open the list) that RHN cannot be contacted.
Comment 2RHEL Program Management
2014-07-24 21:43:46 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I tested this on 6.2.14:
test #1: edit /etc/hosts to point cdn.redhat.com to 127.0.0.1
result: got ssl error (correct)
test #2: block outbound traffic to cdn.redhat.com's IP via iptables
result: got timeout error after a few minutes (correct)
marking closed/currentrelease