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 2254827 - 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
Summary: virt-who is configured and reporting the mapping, but the web ui status shows...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.15.0
Hardware: All
OS: Linux
high
medium
Target Milestone: 6.15.0
Assignee: Chris Roberts
QA Contact: yanpliu
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-16 17:37 UTC by tharring
Modified: 2024-04-23 17:16 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_virt_who_configure-0.5.20
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:16:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
reporting status (87.99 KB, image/png)
2023-12-16 17:37 UTC, tharring 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37054 0 High Assigned virt-who is configured and reporting the mapping, but the web ui status shows “No report yet” and the host will not be c... 2024-01-15 19:44:35 UTC
Github theforeman foreman_virt_who_configure pull 184 0 None open Fixes #37054 - Fix config reporting in the UI 2024-01-15 19:56:23 UTC
Red Hat Issue Tracker SAT-21982 0 None None None 2023-12-16 17:39:48 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:16:27 UTC

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
Note You need to log in before you can comment on or make changes to this bug.