Bug 485085

Summary:	SSM error changing base channel to "System Default Base Channel"
Product:	[Community] Spacewalk	Reporter:	Jay Dobies <jason.dobies>
Component:	WebUI	Assignee:	Jay Dobies <jason.dobies>
Status:	CLOSED NOTABUG	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-03 16:24:09 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

Description Jay Dobies 2009-02-11 15:12:14 UTC

Description of problem:
A null pointer exception is thrown in the logs when I attempt to make the change.

Version-Release number of selected component (if applicable):
Spacewalk 0.5, local build as of Feb 11

How reproducible:
Always

Steps to Reproduce:
1. Selected one system into the SSM
2. Clicked Channels -> Base Channel
3. In the "Desired Base Channel" list, I selected "System Default Base Channel"
4. When I hit confirm, I get an ISE
  
Actual results:
ISE in the UI. Null pointer exception in the logs:

Caused by: java.lang.NullPointerException
	at com.redhat.rhn.frontend.action.channel.ssm.BaseSubscribeAction.confirmUpdateBaseChannels(BaseSubscribeAction.java:172)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[snip]

Expected results:
I'm not fully sure. It's already subscribed to the default channel, so I'm expecting either a confirmation that it was successful or a message that no changes were made.

Additional info:

Comment 1 Jay Dobies 2009-02-11 15:15:18 UTC

This might be related to BZ 420601.

Comment 2 Jay Dobies 2009-02-11 15:21:40 UTC

Another note, this only seems to happen if it is already subscribed to the default channel and I select to subscribe to the default channel. I was able to change to a user created channel and then back to the default channel successfully.

Comment 3 Jay Dobies 2009-03-03 16:24:09 UTC

It looks like this had something to do with the way I syncced my channels. I tried on a 5.3 build that was syncced properly and I don't see the issue.