Bug 1598488

Summary:	virt-who checkin fails with undefined method `[]' for nil:NilClass (NoMethodError)
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-05 16:35:34 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 Justin Sherrill 2018-07-05 15:46:25 UTC

Description of problem:

2018-07-05T15:28:06 [E|bac|4cd3d] undefined method `[]' for nil:NilClass (NoMethodError)
 | /home/vagrant/git/katello/app/lib/actions/katello/host/hypervisors.rb:29:in `block (2 levels) in parse_hypervisors'
 | /home/vagrant/git/katello/app/lib/actions/katello/host/hypervisors.rb:25:in `map'
 | /home/vagrant/git/katello/app/lib/actions/katello/host/hypervisors.rb:25:in `block in parse_hypervisors'
 | /home/vagrant/git/katello/app/lib/actions/katello/host/hypervisors.rb:23:in `each'
 | /home/vagrant/git/katello/app/lib/actions/katello/host/hypervisors.rb:23:in `parse_hypervisors'



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

How reproducible:
always

Steps to Reproduce:
1.  Perform virt-who checking manually 2x  (virt-who -od)

Actual results:
2nd virt-who checkin will fail (first may fail if it was not the first time) 

Expected results:
2nd virt-who checkin should pass

Additional info:

candlepin changed the results from the hypervisor checkin to only include uuids for the 'unchanged' set of hypervisors results

Comment 1 Justin Sherrill 2018-07-05 16:35:34 UTC


*** This bug has been marked as a duplicate of bug 1592281 ***