Bug 1313053

Summary:	[RFE] Delegate subscriptions between organisations
Product:	[Community] Candlepin	Reporter:	Barnaby Court <bcourt>
Component:	candlepin	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.9	CC:	aperotti, csnyder, daniele, sgao
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-20 15:23:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1191822, 1193329

Description Barnaby Court 2016-02-29 19:54:27 UTC

Description of problem:

On physical hosts running as hypervisor (libvirt, openstack compute, etc) that have a RHCI entitlement guests will be entitled to the unlimited virtual subscription partof the same RHCI subscription. The mapping si done using virt-who or katello_notification. However, when the guests on these hypervisors are in different orgnaizations. This does not work

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


How reproducible:


Steps to Reproduce:
1. Build hypervisor with virt-who and RHCI subscription from Sat6 - org1
2. Provision guests from sat6 - org1 on this hypervisor
3. Try to provision guests from sat6 - org2 on this hypervisor

Actual results:

Comment 1 Chris Snyder 2016-09-30 14:42:19 UTC

*** Bug 1004145 has been marked as a duplicate of this bug. ***

Comment 2 Daniele Palumbo 2019-09-20 16:21:05 UTC

Can you please elaborate on the reason for which this bug has been closed?

Comment 3 Barnaby Court 2019-09-20 17:09:49 UTC

There has been no prioritization of this feature from product management for multiple years. If it becomes a priority at some point in the future we will re-open a feature for it. In the meantime, having an RFE that we do not believe will ever be worked on is not useful.