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 906875 - ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
Summary: ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhn-client-tools
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-02-01 18:31 UTC by John Sefler
Modified: 2013-02-04 19:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-02 08:59:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description John Sefler 2013-02-01 18:31:32 UTC 
Description of problem:
Failing to register to RHN on rhel7 


Version-Release number of selected component (if applicable):
[root@jsefler-7 ~]# rpm -q --whatprovides /usr/sbin/rhnreg_ks
rhn-setup-1.8.27-8.el7.noarch


How reproducible:


Steps to Reproduce:
[root@jsefler-7 ~]# rhnreg_ks --serverUrl=https://xmlrpc.rhn.code.stage.redhat.com/XMLRPC --username=qa --password=redhatqa --profilename=rhsm-automation.jsefler-r70-server.usersys.redhat.com --force --norhnsd --nohardware --nopackages --novirtinfo
An error has occurred:
ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
See /var/log/up2date for more information


Actual results:


Expected results:


Additional info:
[Fri Feb  1 13:28:14 2013] up2date ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
[Fri Feb  1 13:28:14 2013] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 218, in <module>
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 96, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhnreg_ks", line 90, in main
    rhnreg.getCaps()
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 237, in getCaps
    s = rhnserver.RhnServer()
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 167, in __init__
    self._server = rpcServer.getServer(serverOverride=serverOverride)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 171, in getServer
    raise up2dateErrors.SSLCertificateFileNotFound(msg)
<class 'up2date_client.up2dateErrors.SSLCertificateFileNotFound'>: ERROR: can not find RHNS CA file: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
Comment 1 Milan Zázrivec 2013-02-02 08:59:22 UTC 
With RHEL-7 (and beyond), you will not be able to register your system
to RHN Classic (as in it's not supported).

Yes, the path "/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT" does not exist
by default, but will become valid once you copy over CA certificate from
your RHN Satellite -- which in fact is the only supported environment
for "classic" registration of a RHEL-7 system.
Note You need to log in before you can comment on or make changes to this bug.