Description of problem:
If a user creates a kickstart profile on an old Satellite (<= 520) and proceeds to upgrade the Satellite to 530, the kickstart profile will migrate over to Cobbler appropriately, but the section within the Cobbler-generated kickstart file related to re-registration will read as thus:

# begin cobbler snippet
# begin Red Hat management server registration
# not configured to register to any Red Hat management server (ok)
# end Red Hat management server registration

Furthermore, if one performs a 'cobbler profile dumpvars --name=<profilename>', the information contained pertaining to the Red Hat management server-related keys will look like this:

 'redhat_management_key': '',
 'redhat_management_permissive': 0,
 'redhat_management_server': '<FQDN of Satellite>',
 'redhat_management_type': 'site'

Version-Release number of selected component (if applicable):

I saw this behavior with the following upgrade scenarios:

520->530, 7/14 build
511->530, 7/14 build
3.7->530, 7/14 build

How reproducible:
Always

Steps to Reproduce:
1. Create an older Satellite (<=520) and create a kickstart profile upon it
2. Upgrade this Satellite to the latest build of 530
3. View the Cobbler-generated kickstart file pertaining to the profile you created or run a 'cobbler profile dumpvars --name=<profilename>'
  
Actual results:
As above

Expected results:
Red Hat management server registration information preserved

Additional info: