Description of problem: When I want to manage some cloned channel, I'm getting ISE. Version-Release number of selected component (if applicable): spacewalk-java-2.0.2-15.el5sat How reproducible: always Steps to Reproduce: 1. Check webUI Channels -> Manage Software Channels -> <some_channel> (I do not know how to create that "<some_channel>", it comes from some old dump and was OK before) Actual results: ISE and traceback in catalina.out Expected results: Form should be displayed
The reason for the ISE is that the imported channel does have filled the 'channel_access' field (private/protected/public). We rely on this field for custom channels. Because there's DEFAULT defined on the rhnChannel table channel_access VARCHAR2(10) DEFAULT ('private'), it looks like the satellite-sync code explicitly set null for this column. Resetting to 'Satellite Synchronization' component.
In reply to Tomas Lestach from comment #3) > The reason for the ISE is that the imported channel does have filled the > 'channel_access' field (private/protected/public). We rely on this field for > custom channels. > > Because there's DEFAULT defined on the rhnChannel table > > channel_access VARCHAR2(10) > DEFAULT ('private'), > > it looks like the satellite-sync code explicitly set null for this column. > Resetting to 'Satellite Synchronization' component. It's less explicit and more just the way that satellite-sync treats all unspecified attributes, but otherwise this is exactly correct. I have added code to check for this so we do not break backwards-compatibility. Committing to Spacewalk master: 99d63c92a987ce66a1a31b66bb993389921739da
Satellite 5.6 has been released. This bug was tracked under the release. This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly before release). Moving to CLOSED CURRENT_RELEASE. Text from Upgrade Erratum follows: 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. http://rhn.redhat.com/errata/RHEA-2013-1395.html