Bug 584781 - Entitlement cert not downloaded in location /etc/pki/entitlement/product
Summary: Entitlement cert not downloaded in location /etc/pki/entitlement/product
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.5
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Todd Sanders
QA Contact: Katello QA List
Depends On:
Blocks: ent2
TreeView+ depends on / blocked
Reported: 2010-04-22 12:00 UTC by spandey
Modified: 2019-09-24 14:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2019-09-24 14:17:34 UTC

Attachments (Terms of Use)

Description spandey 2010-04-22 12:00:36 UTC
Description of problem:

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

How reproducible:

Prerequisites :

Rhel 6 host registered with General candlepin 
sm version 41 

Steps to repro :

Login to the client host with valid credentials 
subscribe for entitlement using cli /gui

expected Result :
Subscribe entitlement certs should present in /etc/pki/entitlement/product/
it should display when execute following command on client console 

subscription-manager-cli list –consumed 

Actual Result 

Not able to find any cert at location /etc/pki/entitlement/product/
Not able to find list of subscribe entitlement using following command  

[root@rhel6client pki]# subscription-manager-cli list --consumed

 	Product Consumed 	activeSubscription 	endDate                   	startDate                 


[root@rhel6client pki]# 

cert contents can be find in 


setup used 

candlepin :
client :

Comment 1 spandey 2010-05-20 09:59:26 UTC
Verified with following setup

server : statler.usersys.redhat.com,cert-fte-candelpin.devlab.redhat.com
client : Rhel6
SM version : 60 

Working fine
certs are getting downloaded in location /etc/pki/entitlement/product using repro steps 

Moving defect status from MODIFIED to VERIFIED

Comment 2 John Sefler 2011-05-04 14:41:29 UTC
Group move of VERIFIED Candlepin component bugs to RELEASE_PENDING

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