Bug 736166

Summary: need certificates from subscription-manager rpm pulled into python-rhsm
Product: Red Hat Enterprise Linux 6 Reporter: Perry Myers <pmyers>
Component: python-rhsmAssignee: Chris Duryee <cduryee>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 6.2CC: cduryee, jsefler
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 17:26:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 682238, 734478, 743047    

Description Perry Myers 2011-09-06 21:28:27 UTC
Description of problem:
For using python-rhsm to register with Hosted candlepin, we need the following certificates to connect:


These certs are in the subscription-manager rpm, but RHEVH doesn't need that rpm (and it pulls in deps like yum, which we also can't use).  So it would be better to move these from s-m to python-rhsm

Comment 1 Chris Duryee 2011-09-07 20:12:11 UTC
0507fb7a6103963f8f9ed4f9e0bb8a934f517124 python-rhsm master 0.96.12+
983fb44fccbf3977ca1ca5d9557503432b791cc5 sub-mgr master 0.96.11+

Comment 3 John Sefler 2011-09-23 14:25:27 UTC
Verifying Version...
[root@jsefler-onprem-62server ~]# rpm -q python-rhsm subscription-manager

[root@jsefler-onprem-62server ~]# rpm -ql python-rhsm | grep .pem
[root@jsefler-onprem-62server ~]# rpm -ql subscription-manager | grep .pem
[root@jsefler-onprem-62server ~]# 

^^^ Notice the ca certificates are now delivered with the python-rhsm and not the subscription-manager package.

Also note that the /etc/rhsm/ca/fakamai-cp1.pem certificate was removed.  This was really used as part of a test environment and is not necessary in the stage/production environment.

Comment 4 errata-xmlrpc 2011-12-06 17:26:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.