Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
When a customer is attempting to use this tool, and their network is unavailable, the error message only points to a general network problem. When a customer contacts GSS we typically ask the same questions:
-- Is your firewall open? ports 80 and 443.
-- Can you ping our server?
-- Can you telnet to our server?
etc..
Full diagnostics steps are here:
https://access.redhat.com/solutions/117723
Is there a way to embed this check into subscription-manager? Or create a new switch (--testnetwork) to perform these steps in an automated fashion?
Ideally, if there is a network problem we tell the customer what the problem likely is and help them fix it themselves.
Apologies Brian but we don't feel this is fixable in any way that will improve what's already there. For the situation as described, the best we can do is report a general network error. We can't really say why your connections are failing or timing out and we're not really the correct location for such a tool.
Closing for now, please reopen is there are strong objections.