RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1387800 - virt-who should report for every hypervisor detected its clusters name
Summary: virt-who should report for every hypervisor detected its clusters name
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.3
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jiri Hnidek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks: 1353215 1387341 1420851 1544891 1546815 1622133 1635187
TreeView+ depends on / blocked
 
Reported: 2016-10-21 23:12 UTC by Andrea Perotti
Modified: 2021-12-10 14:46 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1387341
Environment:
Last Closed: 2018-10-30 10:47:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github /candlepin virt-who pull 167 0 None None None 2020-07-13 03:43:15 UTC
Github candlepin virt-who pull 131 0 None closed 1387800: [RFE] virt-who can report cluster in host-to-guest mapping 2021-02-01 05:22:36 UTC
Red Hat Product Errata RHBA-2018:3169 0 None None None 2018-10-30 10:48:02 UTC

Description Andrea Perotti 2016-10-21 23:12:35 UTC
1. Proposed title of this feature request
Add cluster name into virt-who output.

3. What is the nature and description of the request? 
We need to know the cluster name of one hypervisor host.

4. Why does the customer need this? (List the business requirements here)
We assign the cluster name with a naming convention to understand if the cluster is a PROD or QA one.
We need therefore the cluster name because based on this information we assign the correct subscription based on the SLA.

5. How would the customer like to achieve this? (List the functional requirements here)
We would like to have the cluster name associated to the vmware guest.
In VMWare any host may be applied only to one cluster, therefore is acceptable also to have the cluster name associated with the host.
As we are planning to implement also RHEV, we would like to have a similar feature also for that Hypervisor.

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
virt-who --print, and check in the output for the cluster name of the associated hypervisor host.

8. Does the customer have any specific timeline dependencies?
End of 2016

9. Is the sales team involved in this request and do they have any additional input?
no 

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure

Comment 4 Chris Snyder 2017-08-03 14:59:36 UTC
Andrea,

Is the request to add the cluster name for each hypervisor detected as a fact on the hypervisor consumer? As consumer facts are displayed in the Satellite web UI you should be able to then differentiate between clusters.

Comment 5 Andrea Perotti 2017-08-04 10:03:24 UTC
Customer need this at virt-who level because it parse the output of if and work on assigning subscriptions via API based on the name of the cluster using external tools, like katello-attach-subscription [1] .

[1] https://github.com/RedHatSatellite/katello-attach-subscription

Comment 6 Chris Snyder 2017-08-07 14:39:09 UTC
Andrea,

We'll use this RFE bug to represent the work done on virt-who to gather the cluster name for each hypervisor.

We'll also see what changes can/need to be made to the katello-attach-subscription tool.

Cheers,
Chris

Comment 29 errata-xmlrpc 2018-10-30 10:47:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3169


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