Bug 619326 - M2Crypto.SSL.SSLError: bad end line : error in rhua start
M2Crypto.SSL.SSLError: bad end line : error in rhua start
Status: CLOSED NOTABUG
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: RHUA (Show other bugs)
1.2
All Linux
low Severity medium
: ---
: ---
Assigned To: Jason Dobies
wes hayutin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-29 05:34 EDT by Shveta
Modified: 2010-07-29 09:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-29 09:18:51 EDT
Type: ---
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 Shveta 2010-07-29 05:34:11 EDT
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. created RHUA, CDS through UI
2. ran ./nimbus_setup.py --no-start --skip-deltacloud 
3. copied /tmp/nimbus-rpm to rhua instaled rh-rhua RPM and rhui-tools 
4. rhua start
  
Actual results:


Expected results:


Additional info:

[root@ip-10-204-103-210 nimbus-rpm]# rhui-tools 
Select the component to be configured:
  1 - RHUA
  2 - CDS
  3 - Client
  4 - Entitlement Certificates
Selection:  1

                           -= RHUA Configuration =- 

The following questions are used to configure the RHUA instance.

The host names of the CDS instances that should be managed by this RHUA are
required in this configuration.

Unless otherwise specified, all fields are required.

Local directory in which the RHUA configuration files generated by this tool
should be stored (if this directory does not exist, it will be created):
/tmp/rhua

Directory on the RHUA where packages synchronized to the RHUA will be stored on disk.
If this directory does not already exist, it will be created during the
RHUA configuration:
/mnt/content

Directory on the CDS where the RHUA will upload packages. This value should be the
same as what is specified in the CDS configuration:
/mnt/content

Full path to the content certificate the RHUA will use when downloading
packages from Red Hat:
/root/ssl/entitlement-cert.xml
Cannot find file, please enter a valid path

Full path to the content certificate the RHUA will use when downloading
packages from Red Hat:
/etc/sysconfig/rhn
Cannot find file, please enter a valid path

Full path to the content certificate the RHUA will use when downloading
packages from Red Hat:
/etc/sysconfig/rhn/entitlement-cert.xml

Full path to the content certificate's private key:
/root/ssl/ca.key

Full path to the SSH key that will be used to connect to CDS instances:
/root/ssl/cloude-key.pem

Enter the host names of all CDS instances the RHUA will use, one per line.
To finish inputting instances, enter a blank line.

-> ec2-184-72-166-238.compute-1.amazonaws.com
-> 

Should monitoring features be enabled on the RHUA? If yes, the entitlement
certificates to use to connect the CDS will be specified now. (y/n)
y

Full path to the CA certificate used to sign the entitlement certificates.
/root/ssl/ca.crt

Full path to the entitlement certificates' private key.
/root/ssl/ca.key

Enter the full paths to each entitlement certificate, one per line. The certificate
should be named the same as the channel name for which entitlements are granted
and end with .pem.
To finish inputting certificates, enter a blank line.

-> /root/ssl/build/client-all.crt
-> 

RPM creation successful

RHUA configuration files can be found at /tmp/rhua/rhua/tmp/rh-rhua-config-0.1
RPMs can be found at /tmp/rhua/rhua/build/RPMS



[root@ip-10-204-103-210 ~]# rhui-tools 
Select the component to be configured:
  1 - RHUA
  2 - CDS
  3 - Client
  4 - Entitlement Certificates
Selection:  2    

                           -= CDS Configuration =- 

The following questions are used to configure CDS instances.
Each set of questions describes the configuration for a single CDS.

Unless otherwise specified, all fields are required.

Local directory in which the CDS configuration files generated by this tool
should be stored (if this directory does not exist, it will be created:
/tmp/cds

Directory on the CDS where packages synchronized to the CDS will be stored on disk.
If this directory does not already exist, it will be created during the
CDS configuration:
/mnt/content

Full path to the CDS SSL certificate:
/root/ssl/build/cds01.crt

Full path to the CDS SSL certificate private key:
/root/ssl/server.key

Full path to the CDS SSL certificate's CA certificate:
/root/ssl/ca.crt

Full path to the CDS SSL certificiate's CA chain file (optional):


RPM creation successful

CDS configuration files can be found at /tmp/cds/cds/tmp/rh-cds-config-0.1
RPMs can be found at /tmp/cds/cds/build/RPMS

===================================  
[root@ip-10-204-103-210 ~]# rhua start
The [start] command requires the RHUA be configured. Please run /usr/bin/rhua 'config'
before running this command.
[root@ip-10-204-103-210 ~]# cd /tmp/rhua/rhua/build/RPMS/noarch/
[root@ip-10-204-103-210 noarch]# rpm -ivh rh-rhua-config-0.1-1.noarch.rpm 
Preparing...                ########################################### [100%]
   1:rh-rhua-config         ########################################### [100%]
[root@ip-10-204-103-210 noarch]# rhua start
========================================
RHUA Start

Running RHUA system start
Package directory [/mnt/content] already exists, nothing to do
Synchronizing content
Synchronizing channel list to base [/mnt/content]
Synchronizing channel [rhel-i386-server-5] and creating repo
Traceback (most recent call last):
  File "/usr/bin/rhua", line 21, in ?
    rhua.cli.main(sys.argv)
  File "/usr/lib/python2.4/site-packages/rhua/cli.py", line 102, in main
    func(options, *args[2:])
  File "/usr/lib/python2.4/site-packages/rhua/rhua.py", line 69, in start
    num_packages = package_ops.sync(options)
  File "/usr/lib/python2.4/site-packages/rhua/package_ops.py", line 55, in sync
    report = g.fetchYumRepo(basepath=channel_path)
  File "/usr/lib/python2.4/site-packages/grinder/RepoFetch.py", line 179, in fetchYumRepo
    self.yumFetch.getRepoData()
  File "/usr/lib/python2.4/site-packages/grinder/RepoFetch.py", line 103, in getRepoData
    for ftype in self.repo.repoXML.fileTypes():
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 1392, in <lambda>
    repoXML = property(fget=lambda self: self._getRepoXML(),
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 1384, in _getRepoXML
    self._loadRepoXML(text=self)
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 1374, in _loadRepoXML
    return self._groupLoadRepoXML(text, ["primary"])
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 1358, in _groupLoadRepoXML
    if self._commonLoadRepoXML(text):
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 1204, in _commonLoadRepoXML
    result = self._getFileRepoXML(local, text)
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 985, in _getFileRepoXML
    cache=self.http_caching == 'all')
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 816, in _getFile
    result = self.grab.urlgrab(misc.to_utf8(relative), local,
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 506, in <lambda>
    grab = property(lambda self: self._getgrab())
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 501, in _getgrab
    self._setupGrab()
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 486, in _setupGrab
    ssl_context = self._getSslContext())
  File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 646, in _getSslContext
    sslCtx.load_cert(self.sslclientcert, self.sslclientkey)
  File "/usr/lib64/python2.4/site-packages/M2Crypto/SSL/Context.py", line 72, in load_cert
    m2.ssl_ctx_use_cert(self.ctx, certfile)
M2Crypto.SSL.SSLError: bad end line
Comment 1 wes hayutin 2010-07-29 09:18:51 EDT
the repo that the rhua pulls from has moved to the hosted cds.
We'll need to get you the updated info. We're working that out now.

Closing this bug..

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