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.
Internal server error is in truth a problem on the server side.
When the client receives HTTP/500 response, there's not much it can
do about it -- other than display it.
May I suggest to reach out to RHN hosted folks (or admins) to investigate
the issue further (seeing this is an rhn.qa environment, problems like this
are nothing unusual).
But there is no error message, there is traceback. User shouldn't see any traceback.
Comment 3Jan Pazdziora (Red Hat)
2011-11-24 13:29:31 UTC
If I set serverURL in /etc/sysconfig/rhn/up2date to point to URL which always returns 500 (ISE), I get a nice error message "We could not contact Satellite or Proxy at ...", which comes from _chooseServerPageApply.
So if the server returns 500 (ISE) in consistent manner, the user will see a nice error message right at the beginning.
If the first page passes thou, we don't catch the exceptions much beyond this point and leave it on firstboot to handle it, thus the tracebacks.
I am not sure the effort to address all the places where the exception can appear and to QA it is worth the benefit, with subscription manager being available.
I therefore propose WONTFIX, while acknowledging that we would probably be able to address it properly given we spend enough man hours on the issue.
Mike, could you give the product management's ruling on this bug?