Description of problem:
During firstboot, if there is a server-side issue with subscriptions.rhn.redhat.com, the user will be presented with a "network error" message. This can lead to the user digging through network issues on their end, when in reality their only recourse is to simply wait for the issue to be fixed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. induce a 500 error (either take down QA candlepin for a minute, or alter rhsm.conf to point to a page with a 500 error)
2. run subscription-manager or firstboot, click through as normal using any user
user gets a "network error" message
user gets a message saying "We are unable to process your request at this time. Please try again later" (or something to that effect).
There probably just needs to be a new exception put into client/python-rhsm/src/rhsm/connection.py, alongside NetworkException, and then appropriate handlers in the higher-level app code.
Introducing an apache error causes a "RemoteServerException" now instead of the generic NetworkException.
Tested by changing the prefix in the rhsm.conf to a bogus value.
tested working in:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.