The 500 change of rhnConfigChannel changes users data. It is NOT completely a schema change. It is NOT default data for a table. However, it must be run on old satellites while they migrate their data to a new version of satellite.
looks like an upgrade bug, giving to cperry
this was included as part of the sat 500 upgrade script. testplan --------- 1) using config channel mgmt sat feature, generate all combinations of data (i.e., server import, local override, and normal). 2) upgrade scehma 3) config channels continue to work as before.
QA Verified, after upgrade the configuration work set in a 420 satellite appears to have migrated correctly over after an upgrade to 500
release_pending
Closed for Satellite 500 Release.