Bug 2254827

Summary: virt-who is configured and reporting the mapping, but the web ui status shows “No report yet” and the host will not be considered as Virtual Host guest
Product: Red Hat Satellite Reporter: tharring
Component: Virt-who Configure PluginAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: yanpliu <yanpliu>
Severity: medium Docs Contact:
Priority: high    
Version: 6.15.0CC: ahumbe, chrobert, lufu, rlavi, yanpliu, zhunting
Target Milestone: 6.15.0Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
URL: https://projects.theforeman.org/issues/37054
Whiteboard:
Fixed In Version: rubygem-foreman_virt_who_configure-0.5.20 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:16:26 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:
Attachments:
Description Flags
reporting status none

Description tharring 2023-12-16 17:37:09 UTC
Created attachment 2004589 [details]
reporting status

Description of problem:
- virt-who is configured with vcenter and reporting the mapping, but the web ui status shows “No report yet” and the host will not be considered as a Virtual Host guest 

Version-Release number of selected component (if applicable):
- satellite-6.15.0-2.el8sat.noarch

How reproducible: 100%


Steps to Reproduce:
1. Configure virt-who via web UI and deploy it
2. Tested with and without whitelisting the hypervisors and the same result

Actual results:
-  web ui, Infrastructure, Virt-who configuration shows the status “No report yet” even though the hypervisors shows up under web ui, Hosts, All Hosts
- web ui, Hosts, Content Host, target host, Legacy Content Host UI, there is no hypervisor listed under “Virtual Host”


Expected results:
- web ui, Infrastructure, Virt-who configuration should show the status with green circle and the date.
- web ui, Hosts, Content Host, target host, Legacy Content Host UI, there should be hypervisor listed under “Virtual Host”


Additional info:
This will impact the inventory in console.redhat.com due to SCA enablement

Comment 3 tharring 2023-12-16 17:41:38 UTC
The virt-who is mapping as below - 

[root@ito-sat615 ~]# egrep -i "name|5a760d42-9b50-855b-b34e-fbd058ed175e" /tmp/virt-who.log
            "name": "esxi4.lab.eng.rdu2.redhat.com",
            "name": "esxi1.lab.eng.rdu2.redhat.com",
            "name": "esxi2.lab.eng.rdu2.redhat.com",
                    "guestId": "5a760d42-9b50-855b-b34e-fbd058ed175e",      <<<<< This is the test host (ito_vm8) that is not considered to be virtual guest in the attachment 'no hyperviros'
            "name": "esxi3.lab.eng.rdu2.redhat.com",

Comment 5 Bryan Kearney 2024-01-18 20:02:37 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37054 has been resolved.

Comment 7 Bryan Kearney 2024-01-25 12:02:43 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37054 has been resolved.

Comment 22 errata-xmlrpc 2024-04-23 17:16:26 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 (Important: Satellite 6.15.0 release), 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/RHSA-2024:2010