Bug 1254266 - type error in rhn exception during rhn_check
Summary: type error in rhn exception during rhn_check
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Dobes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 14:22 UTC by Pavel Studeník
Modified: 2018-04-09 14:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-09 14:46:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2015-08-17 14:22:47 UTC
Problem is only on Satellite 5.6

package: spacewalk-backend-2.0.3-36.el6sat.noarch

file: /backend/common/rhnException.py

$ rhn_check 
...
 Error Class Code: 9
 Error Class Info: Invalid System Credentials.
 Explanation: 
-     An error has occurred while processing your request. If this problem
+     An error has occured while processing your request. If this problem
      persists please consult the Red Hat Customer Portal Knowledge Base
      landing page on common registration Error Class Codes at
      https://access.redhat.com/solutions/17036 for a possible resolution.


Actual results:
An error has occured while processing your request. If this problem

Expected results:
An error has occurred while processing your request. If this problem

Comment 1 Tomas Lestach 2018-04-09 14:46:30 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.


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