Description of problem: Observed that two client were able to register with the same consumer id and both were able to subscribe for subscriptions Version-Release number of selected component (if applicable): subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.8.2-1 subscription-manager: 1.8.5-1.git.4.82e4aee.el7 python-rhsm: 1.8.8-1.git.0.c7ea5c0.el7 How reproducible: Steps to Reproduce: 1.Register client A with candlepin and attach subscription [root@rhel7hudson ~]# subscription-manager register Username: admin Password: Organization: admin The system has been registered with id: 880f56b3-a194-400f-85b8-23fff751b185 [root@rhel7hudson ~]# subscription-manager list --available | more +-------------------------------------------+ Available Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Server Bundled SKU: awesomeos-server Pool ID: 8ac6a30b3ded5a27013ded5aea290596 Quantity: 5 Service Level: Premium Service Type: Level 3 Multi-Entitlement: No Ends: 04/09/2014 System Type: Physical Subscription Name: RAM Limiting Package (8GB) SKU: ram-8gb Pool ID: 8ac6a30b3ded5a27013ded5ae2ec02db Quantity: 5 Service Level: Service Type: Multi-Entitlement: No Ends: 04/09/2014 System Type: Physical Subscription Name: Shared File System SKU: sfs Pool ID: 8ac6a30b3ded5a27013ded5ae34c02f7 Quantity: 5 Service Level: Layered Service Type: Multi-Entitlement: No Ends: 04/09/2014 System Type: Physical Subscription Name: Awesome OS for x86_64/i686/ia64/ppc/ppc64/s390x/s390 [root@rhel7hudson ~]# subscription-manager attach --pool 8ac6a30b3ded5a27013ded5aea290596 Successfully attached a subscription for: Awesome OS Server Bundled [root@rhel7hudson ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Server Bundled Provides: Clustering Bits Awesome OS Server Bits Load Balancing Bits Large File Support Bits Shared Storage Bits Management Bits SKU: awesomeos-server Contract: 6 Account: 12331131231 Serial Number: 2301919385337369596 Pool ID: 8ac6a30b3ded5a27013ded5aea290596 Active: True Quantity Used: 1 Service Level: Premium Service Type: Level 3 Starts: 04/09/2013 Ends: 04/09/2014 [root@rhel7hudson ~]# subscription-manager identity Current identity is: 880f56b3-a194-400f-85b8-23fff751b185 name: rhel7hudson org name: Admin Owner org id: admin 2.Now register client B with client A's consumed id [root@rheltest ~]# subscription-manager register --consumerid=880f56b3-a194-400f-85b8-23fff751b185 Username: admin Password: The system has been registered with id: 880f56b3-a194-400f-85b8-23fff751b185 [root@rheltest ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Server Bundled Provides: Clustering Bits Awesome OS Server Bits Load Balancing Bits Large File Support Bits Shared Storage Bits Management Bits SKU: awesomeos-server Contract: 6 Account: 12331131231 Serial Number: 2301919385337369596 Pool ID: 8ac6a30b3ded5a27013ded5aea290596 Active: True Quantity Used: 1 Service Level: Premium Service Type: Level 3 Starts: 04/09/2013 Ends: 04/09/2014 [root@rheltest ~]# subscription-manager identity Current identity is: 880f56b3-a194-400f-85b8-23fff751b185 name: rhel7hudson org name: Admin Owner org id: admin 3. Try attaching new subscription on client B [root@rheltest ~]# subscription-manager attach --pool 8ac6a30b3ded5a27013ded5ae2ec02db Successfully attached a subscription for: RAM Limiting Package (8GB) [root@rheltest ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Server Bundled Provides: Clustering Bits Awesome OS Server Bits Load Balancing Bits Large File Support Bits Shared Storage Bits Management Bits SKU: awesomeos-server Contract: 6 Account: 12331131231 Serial Number: 2301919385337369596 Pool ID: 8ac6a30b3ded5a27013ded5aea290596 Active: True Quantity Used: 1 Service Level: Premium Service Type: Level 3 Starts: 04/09/2013 Ends: 04/09/2014 Subscription Name: RAM Limiting Package (8GB) Provides: RAM Limiting Product SKU: ram-8gb Contract: 138 Account: 12331131231 Serial Number: 1029145506555988830 Pool ID: 8ac6a30b3ded5a27013ded5ae2ec02db Active: True Quantity Used: 1 Service Level: Service Type: Starts: 04/09/2013 Ends: 04/09/2014 4. Now try attaching new subscription on client A [root@rhel7hudson ~]# subscription-manager attach --pool 8ac6a30b3ded5a27013ded5ae33202ee Successfully attached a subscription for: Shared File System [root@rhel7hudson ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Server Bundled Provides: Clustering Bits Awesome OS Server Bits Load Balancing Bits Large File Support Bits Shared Storage Bits Management Bits SKU: awesomeos-server Contract: 6 Account: 12331131231 Serial Number: 2301919385337369596 Pool ID: 8ac6a30b3ded5a27013ded5aea290596 Active: True Quantity Used: 1 Service Level: Premium Service Type: Level 3 Starts: 04/09/2013 Ends: 04/09/2014 Subscription Name: RAM Limiting Package (8GB) <---- subscription from Client B Provides: RAM Limiting Product SKU: ram-8gb Contract: 138 Account: 12331131231 Serial Number: 1029145506555988830 Pool ID: 8ac6a30b3ded5a27013ded5ae2ec02db Active: True Quantity Used: 1 Service Level: Service Type: Starts: 04/09/2013 Ends: 04/09/2014 Subscription Name: Shared File System <-- new attached subscription on client A Provides: Shared File System Bits SKU: sfs Contract: 133 Account: 12331131231 Serial Number: 6712075614170298971 Pool ID: 8ac6a30b3ded5a27013ded5ae33202ee Active: True Quantity Used: 1 Service Level: Layered Service Type: Starts: 04/09/2013 Ends: 04/09/2014 Actual results: Observed that both the client's were active and was able to attach subscriptions Expected results: client A should unregister once the client B is registered with the same consumer'id and All subscription should unsubscribe from Client A ?? Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
As we are going to parallel the Satellite behavior, this will not be fixed as it occurs the same way there.
sure... I like this appraoch.