Bug 2070253 - When installing virt-who on RHV hypervisor, both entries will be available on Satellite webUI (hypervisor and virt-who-hypervisor-1) [NEEDINFO]
Summary: When installing virt-who on RHV hypervisor, both entries will be available on...
Keywords:
Status: NEW
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: 2022-08-23 14:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
redakkan: needinfo? (wpinheir)


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 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.


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