Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1652732

Summary: Virt-who reported host on Satellite WEB-UI , under Hosts---> Content Hosts shows "Type" as blank
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: Hosts - ContentAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: egolov
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.10.0.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:39:05 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
Screenshot for reference none

Description Satyajit Das 2018-11-22 17:56:09 UTC
Created attachment 1508062 [details]
Screenshot for reference

Description of problem:

Virt-who reported  host on Satellite WEB-UI , under Hosts---> Content Hosts shows "Type" as blank

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

satellite-6.4.0-15.el7sat.noarch

virt-who-0.22.5-1.el7.noarch

How reproducible:

100%

Steps to Reproduce:
1.Configure/Deploy the virt-who using the (UI -> Infrastructure -> Virt-who configurations). The configuration deployed successfully.
2. Check the status (UI -> Hosts -> Content Hosts ->virt-who-<FQDN>)

Actual results:

Type is not getting populated, as it is showing as blank.


Expected results:

Type should be specified to identify the hypervisor type.


Additional info:

Comment 4 John Mitsch 2019-01-09 19:51:36 UTC
Created redmine issue https://projects.theforeman.org/issues/25818 from this bug

Comment 5 John Mitsch 2019-01-09 20:08:55 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25819 from this bug

Comment 6 John Mitsch 2019-01-09 20:09:25 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25415 from this bug

Comment 7 Bryan Kearney 2019-01-10 13:12:48 UTC
Upstream bug assigned to jomitsch

Comment 8 Bryan Kearney 2019-01-10 13:12:50 UTC
Upstream bug assigned to jomitsch

Comment 9 Bryan Kearney 2019-01-17 15:07:27 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25819 has been resolved.

Comment 13 errata-xmlrpc 2019-05-14 12:39:05 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/RHSA-2019:1222