Bug 1311768 - rhn_register incorrectly reports that RHNS-CA-CERT has expired
rhn_register incorrectly reports that RHNS-CA-CERT has expired
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Registration (Show other bugs)
_unset
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Bernleithner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-24 18:37 EST by noah davids
Modified: 2017-07-05 11:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description noah davids 2016-02-24 18:37:32 EST
Description of problem:
rhn_register reports a Fatal Error "The certificate /usr/share/rhn/RHNS-CA-CERT is expired. Please ensure you have the correct certificate and your system time is correct." When what is really wrong is that the serverURL value in /etc/sysconfig/rhn/up2date is not set to https://xmlrpc.rhn.redhat.com/XMLRPC.


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. set serverURL= to a host that has an HTTPS server and is not xmlrpc.rhn.redhat.com/XMLRPC

2. run rhn_register

Actual results:
You get an error message indicating that the /usr/share/rhn/RHNS-CA-CERT has expired.

Expected results:
You should get an error indicating that the wrong server has been reached or at least an indication that the server which should be clearly identified could not be validated with the RHNS-CA-CERT.

Additional info:
The customer was using the serverURL of rhn.redhat.com/XMLRPC -- note (which I did not) that the xmlrpc is missing from the host name. I also tried it with www.google.com and got the same results.
Comment 1 Thomas "Shea" DeAntonio 2017-07-05 11:12:46 EDT
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 11:13:32 EDT
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).

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