Bug 578148 - Allowed multiple subscribe for specific pool or product
Summary: Allowed multiple subscribe for specific pool or product
Keywords:
Status: CLOSED DUPLICATE of bug 582223
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Bryan Kearney
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-30 12:12 UTC by spandey
Modified: 2015-05-14 15:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-29 14:57:09 UTC
Embargoed:


Attachments (Terms of Use)

Description spandey 2010-03-30 12:12:48 UTC
Description of problem:


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


How reproducible:
100%

Prerequisites 
Properly configured candlepin Host
subscription manager rpm version 26

Steps to Repro :

Login to Rhel6 client with valid credentials.
Installed subscription manager RPM and edited rhsm.conf for candlepin Host
Subscribe for product using poolid using following command 

subscription-manager-cli subscribe –pool=1
subscription-manager-cli subscribe –pool=1
subscription-manager-cli subscribe –pool=1
subscription-manager-cli subscribe –pool=1

Expected Result : 
At second subscription of same pool message should display 

Already registered for pool = 1

Actual Result : 
At every attempt new cert has been downloaded  in /etc/pki/entitlement/product. And pool count has been reduced at candlepin side .

Comment 2 RHEL Program Management 2010-03-30 13:22:08 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 James Bowes 2010-04-29 14:57:09 UTC

*** This bug has been marked as a duplicate of bug 582223 ***


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