This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2070253 - When installing virt-who on RHV hypervisor, both entries will be available on Satellite webUI (hypervisor and virt-who-hypervisor-1)
Summary: When installing virt-who on RHV hypervisor, both entries will be available on...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-who
Version: 9.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: yuefliu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-30 17:50 UTC by Waldirio M Pinheiro
Modified: 2023-09-22 13:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 13:54:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34863 0 Normal New When installing virt-who on RHV hypervisor, both entries will be available on Satellite webUI (hypervisor and virt-who-h... 2022-05-04 20:48:24 UTC
Red Hat Issue Tracker   RHEL-7152 0 None Migrated None 2023-09-22 13:54:16 UTC
Red Hat Issue Tracker RHELPLAN-122595 0 None None None 2022-05-19 13:34:00 UTC

Description Waldirio M Pinheiro 2022-03-30 17:50:53 UTC 
Description of problem:
For RHV environment, the customer is registering the hypervisor via Satellite. However, when installing virt-who on hypervisor itself, a new entry "virt-who-<hypervisor_fqdn>-<org_id>" is created and the customer is not happy with that.

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


How reproducible:
100%

Steps to Reproduce:
1. Register the hypervisor to satellite
2. Install virt-who on the hypervisor
3. Check in Satellite webUI

Actual results:
Two entries, hypervisor and virt-who-hypervisor-1

Expected results:
Only one entry, maybe hypervisor

Additional info:
For this kind of scenario, to track all the hypervisors, we can check on the Content Host pages and filter by "hypervisors = true". This will bring back all the hypervisors systems.
Comment 1 Lucy Fu 2022-05-04 20:48:24 UTC 
Created redmine issue https://projects.theforeman.org/issues/34863 from this bug
Comment 2 Bryan Kearney 2022-05-06 00:04:54 UTC 
Upstream bug assigned to mhulan
Comment 3 Bryan Kearney 2022-05-06 00:04:56 UTC 
Upstream bug assigned to mhulan
Comment 5 Bryan Kearney 2022-05-18 20:04:36 UTC 
Upstream bug assigned to mhulan
Comment 6 Bryan Kearney 2022-05-18 20:04:38 UTC 
Upstream bug assigned to mhulan
Comment 7 William Poteat 2022-05-19 13:26:00 UTC 
The issue is that libvirt is reporting a different uuid than subscription manager for the hypervisor system.

example config:

[libvirt-test]
type=libvirt
server=qemu:///system
owner=admin
hypervisor_id=hostname

I saw it on Fedora 35.
Comment 22 RHEL Program Management 2023-09-22 13:51:44 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 23 RHEL Program Management 2023-09-22 13:54:24 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.