Bug 488822

Summary: ISE when viewing packages that need upgrading but have no errata
Product: [Community] Spacewalk Reporter: Mike McCune <mmccune>
Component: WebUIAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-09 20:33:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 456553    
Attachments:
Description Flags
stacktrace none

Description Mike McCune 2009-03-05 20:38:11 UTC
Using rhnpush do the following:

* Create a system that is RHEL5.1 
* Create a channel that has RHEL 5.2
* Create activation key for 5.2 channel
* Register said system to Spacewalk using activation key
* GUI should show that your system needs upgraded packages since channel is newer than 5.1
* Try to click on the # of packages needing upgrades from the "Packages" column on:

https://<spacewalk>/rhn/systems/Overview.do 

Should take you to:

https://<spacewalk>/rhn/systems/details/packages/UpgradableList.do?sid=*****

This causes:

Caused by: java.lang.NullPointerException
	at com.redhat.rhn.frontend.dto.UpgradablePackageListItem.getErrata(UpgradablePackageListItem.java:107)
	at sun.reflect.GeneratedMethodAccessor338.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Full dump incoming.

Comment 1 Mike McCune 2009-03-05 20:38:50 UTC
Created attachment 334207 [details]
stacktrace

Comment 2 Brad Buckingham 2009-03-09 20:33:29 UTC
This BZ is a duplicate of bz 486982 and a fix has already been submitted.  Ran tests with the latest code and was not able to reproduce the issue.

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