Bug 1777522

Summary:	Virt-who Configurations page on the Red Hat Satellite WebUI shows status as "No Report Yet"
Product:	Red Hat Satellite	Reporter:	Varatharaja Perumal G <vgunasek>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	jturel, mhulan, mmccune, patalber, susalvi, wpoteat
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:27:30 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:

Description Varatharaja Perumal G 2019-11-27 17:52:49 UTC

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:

Comment 8 Surjeet Salvi 2020-01-31 09:02:37 UTC

Hello Team,

Could you please provide an update on the Bugzilla.

Regards
Surjeet

Comment 9 Jonathon Turel 2020-02-07 14:08:09 UTC

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.

Comment 16 Cole Higgins 2020-03-12 19:32:57 UTC

Verified in 6.7 snap 15 

Last reported time is shown after Virt-who deploy

Comment 19 errata-xmlrpc 2020-04-14 13:27:30 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-2020:1454