Bug 1267007 – NullPointerException in Exporter.java when null Product is provided

Bug 1267007 - NullPointerException in Exporter.java when null Product is provided

Summary:	NullPointerException in Exporter.java when null Product is provided

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Candlepin
Classification:	Community
Component:	candlepin (Show other bugs)
Sub Component:
Version:	0.9
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	candlepin-bugs
QA Contact:	Katello QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-28 15:26 EDT by Jonathon Turel
Modified:	2015-09-29 10:26 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-09-29 10:26:56 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jonathon Turel 2015-09-28 15:26:07 EDT

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Mock the Exporter.java spec tests to receive null Products in getProductById

Actual results:

NullPointerException is thrown, preventing the export from completing. This breaking manifest generation.


Expected results: Manifest should generate successfully. We log the fact that a product was null or missing content in the IT Adapters.


Additional info:

Relevant splunk query: https://splunk.corp.redhat.com/en-US/app/search/search?sid=1443199695.789193.splunk-src02.intranet.prod.int.phx2.redhat.com

Comment 1 Filip Nguyen 2015-09-29 10:26:56 EDT

Export works differently in CP 2.0 (no longer calls adaptor). So this might not be an issue

0.9 is not long term supported, so we will not fix it in 0.9

Note You need to log in before you can comment on or make changes to this bug.