Description of problem:
After upgrading from 5.2 to 5.4 Satellite, taskomatic was failing to star on
customer's Satellite. It seems that all their kickstart profile names (~250)
were invalid (contained dots) by 5.3/5.4 Satellite standard which only allows
alphanumeric names, and once they renamed them everything was fine.

Customer:
"Since clobber is introduced in 5.3 and 5.4, it cannot seem to recognize the
kickstart profiles and goes thru every profile (all 250 of them), and it's
possible that since clobber's instance starts before taskomatic...having to go
thru 250 (takes longer than 30secs) profiles causes taskomatic to time out
(30secs) and fail. Not sure why during the upgrade, it fails to convert the
labels to 5.4 standards, or maybe it was not part of the upgrade." 

Can we provide a step/script in rhn-upgrade to convert any ks profile names that're no longer valid?  Just filter out non-alphanumeric chars or give user a listing and option to rename them with their choice.

Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.3.0 and 5.4.0

How reproducible:
Always.

Steps to Reproduce:
1. Have 5.2.0 or earlier Satellite with kickstart profile names including alphanumeric characters.
2. Upgrade to 5.4.0 Satellite.

Actual results:
Taskomatic can't be started, and cobbler issues. Invalid kickstart profile names.

Expected results:
Prompt user and provide ability to convert ks profile names during upgrade.

Additional info:
See related Bug 679970 - Satellite 5.3+ Release Notes & Upgrade documentation: include kickstart profile naming requirement change (alphanumeric) and need to convert names during upgrade