Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1787070 - [RFE] Cross organization VM/hypervisor mapping for VM subscription allocation
Summary: [RFE] Cross organization VM/hypervisor mapping for VM subscription allocation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.6.0
Hardware: All
OS: Linux
unspecified
medium with 1 vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-30 17:33 UTC by João Saraiva
Modified: 2023-01-20 16:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-09 17:02:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description João Saraiva 2019-12-30 17:33:30 UTC
Description of problem:
In the same satellite server if you have one organization managing hypervisors and their subscriptions and other organizations managing the VMs running on those hypervisors (and other physical servers), the VMs cannot obtain a valid subscription because the organizations managing them have no visibility on the VM/hypervisor mapping reported by the virt-who instance configured in the organization that manages the hypervisors.
Configuring a virt-who instance in each of the organizations managing the VMs implies that those organizations have to have subscriptions for the hypervisors which would result in subscribing the same hypervisors many times and wasting subscriptions which doesn't make sense.
Otherwise everything would have to be in one organization. In companies where different departments manage their own subscriptions we cannot have only one satellite organization, that's not a good solution.

Comment 3 Mike McCune 2021-03-16 15:58:33 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Colum Gaynor 2021-06-17 11:07:48 UTC
Mike - We (Nokia Global Account Team) had a meeting with the Nokia IT team which raised this Bugzilla just today.
Are you able to provide us a little bit more customer friendly rationale for the decision ?
I promised João to track the Bugzilla status. This is the only RFE request from that team currently

Colum Gaynor - Senior Customer Success Manager - CEE Focused soltuions + Nokia Global Account Team

Comment 5 Mike McCune 2021-07-09 17:02:24 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


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