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.
Bug 668814 - firstboot and subscription-manager display "network error" on server 500
Summary: firstboot and subscription-manager display "network error" on server 500
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Chris Duryee
QA Contact: John Sefler
Depends On:
Blocks: Entitlement-Beta
TreeView+ depends on / blocked
Reported: 2011-01-11 17:22 UTC by Chris Duryee
Modified: 2011-05-19 13:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-05-19 13:38:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0611 0 normal SHIPPED_LIVE new package: subscription-manager 2011-05-18 17:56:21 UTC

Description Chris Duryee 2011-01-11 17:22:16 UTC
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):


How reproducible:

every time

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

Actual results:

user gets a "network error" message

Expected results:

user gets a message saying "We are unable to process your request at this time. Please try again later" (or something to that effect).

Additional info:

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.

Comment 4 J.C. Molet 2011-01-20 16:58:34 UTC
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:

Comment 5 errata-xmlrpc 2011-05-19 13:38:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.