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." 

There seems to be no indication of the profile naming requirements change in Satellite 5.3 or 5.4 Release Notes:
http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3/html/Release_Notes/index.html
http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4/html-single/Release_Notes/index.html

...or the rhn-upgrade documentation.

This BZ is for including a blurb in above documentation about kickstart profile naming requirements and customer needing to convert the names when upgrading from 5.2 or earlier Satellites.

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. Read Release Notes and upgrade documentation.

Actual results:
(see above)

Expected results:
(see above)

Additional info: