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_server': '<FQDN of Satellite>',
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
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>'
Red Hat management server registration information preserved
Working on this currently.
VERIFIED on 7/22 build.
rlx-2-04 4.2 ->5.3 upgrade
rlx-3-08 4.0 -> 5.3 upgrade
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.