Bug 708372

Summary: Update the text of rhnException(9)
Product: [Retired] Red Hat Network Reporter: Šimon Lukašík <slukasik>
Component: RHN/BackendAssignee: rhn-dev-list
Status: CLOSED EOL QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: RHN StableCC: nbronson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Šimon Lukašík 2011-05-27 13:40:34 UTC
Description of problem:
Steps to Reproduce:
1. install rhel4/5/6
2. remove your systemid
3. rhn-channel -l
  
Actual results:
Error communicating with server. The message was:

Error Message:
    Please run rhn_register (or up2date                     --register on Red Hat Enterprise Linux 3 or later)
                    as root on this client
Error Class Code: 9
Error Class Info: Invalid System Credentials.
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.


Expected results:
As per year 2011, one would suppose somewhat different suggestion 
then: up2date --register on Red Hat Enterprise Linux 3

Additional info:
rhel4 does include rhn_register command. up2date --register applies only
for rhel3 clients. And as such it could be dropped.

Comment 1 Thomas "Shea" DeAntonio 2017-07-05 15:12:37 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

Comment 2 Thomas "Shea" DeAntonio 2017-07-05 15:13:24 UTC
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).