Bug 1319872

Summary:	Error when converting edeploy data
Product:	Red Hat OpenStack	Reporter:	Lucas Alvares Gomes <lmartins>
Component:	openstack-ironic-inspector	Assignee:	Lucas Alvares Gomes <lmartins>
Status:	CLOSED ERRATA	QA Contact:	Raviv Bar-Tal <rbartal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.0 (Liberty)	CC:	mburns, rbartal, slinaber
Target Milestone:	---
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-inspector-2.2.5-2.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-07 21:49:32 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 Lucas Alvares Gomes 2016-03-21 17:44:38 UTC

Description of problem:

When attempting to convert some eDeploy data to integer, inspector will handle the ValueError exception which works fine for strings that are not interger-like. But, when this data is None a TypeError exception will be raised and that's not being handled, resulting in the following error:

Introspection for UUID c5a871a2-ae4a-4057-b9c4-a9daaf8b276c finished with error: Unexpected exception TypeError during processing: int() argument must be a string or a number, not 'NoneType'

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


How reproducible:
openstack-ironic-inspector-2.2.4-3.el7ost.noarch

Steps to Reproduce:
1. Just start inspection
2.
3.

Actual results:

Inspection fails with:

Introspection for UUID c5a871a2-ae4a-4057-b9c4-a9daaf8b276c finished with error: Unexpected exception TypeError during processing: int() argument must be a string or a number, not 'NoneType'

Expected results:

Inspection to pass 

Additional info:

Comment 4 errata-xmlrpc 2016-04-07 21:49:32 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://rhn.redhat.com/errata/RHEA-2016-0604.html