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.

Description of problem:

Virt-who Configurations page on the Red Hat Satellite WebUI shows status as "No Report Yet" hypervisors have a updated guest mapping list and the configuration is working fine.


Version-Release number of selected component (if applicable):
satellite-6.5.2.1-1.el7sat.noarch
virt-who-0.24.7-1.el7.noarch

Steps to Reproduce:
1. Configure/Deploy the virt-who using the (UI -> Infrastructure -> Virt-who configurations).
2. Check the status (UI -> Infrastructure -> Virt-who configurations)


Actual results:

Actions::Katello::Host::Hypervisors completed with warning result.

[E|bac|] undefined method `[]' for nil:NilClass (NoMethodError)
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.12.0.27/app/lib/actions/katello/host/hypervisors.rb:23:in `block in parse_hypervisors'


Expected results:


Virt-who reported profile should have the last reported information.

Additional info:

Hello Team,

Could you please provide an update on the Bugzilla.

Regards
Surjeet

Hello Varatharaja,

Please provide the virt-who report which is causing the problem. I'm fairly certain this has been fixed in 6.6 but would like to confirm that.

Verified in 6.7 snap 15 

Last reported time is shown after Virt-who deploy

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-2020:1454