Description of problem:
A taskomatic task "KickstartFileSyncTask" will be repeated endlessly for
kickstart profiles renamed before upgrade to Satellite 5.5.

Version-Release number of selected component (if applicable):
spacewalk-taskomatic-1.7.54-100

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a 5.4 Satellite, kickstart profile "profile01"
2. Rename "profile01" to "profile02"
2. Upgrade to Satellite 5.5
3. Check taskomatic & cobbler logs after upgrade
  
Actual results:
1. Taskomatic will endlessly try to run KickstartFileSyncTask for kickstart
profile "profile02", leaving messages like:

com.redhat.rhn.taskomatic.task.KickstartFileSyncTask - Syncing profile02

in /var/log/rhn/rhn_taskomatic_daemon.log

2. kickstart path for the "profile02" profile will not be updated in
cobbler's records.


Expected results:
1. Kickstart profile "profile02" will be synced only once.
2. kickstart path for the "profile02" profile will be updated in
cobbler's records.

Additional info:
On Satellite before the upgrade:
1. Kickstart file for "profile01" is at

      /var/lib/rhn/kickstarts/wizzard/profile01.cfg

2. cobbler's record for "profile01" points to the above file.
3. "profile01" will be renamed to "profile02"
4. Kickstart file for "profile02" will still be

      /var/lib/rhn/kickstarts/wizzard/profile01.cfg

5. cobbler's record will remain unchanged

During the upgrade to Satellite 5.5, content of

    /var/lib/rhn/kickstarts/wizzard/

will be deleted.

After the upgrade to Satellite 5.5, "KickstartFileSyncTask" will wake up.

The taskomatic task "KickstartFileSyncTask" does the following:
1. Lists all available kickstart profiles
2. For every kickstart profile, it contacts cobbler and asks for the path to
the kickstart file for the kickstart profile. Next, it checks whether
the kickstart file is present on the filesystem. If not, it creates this
file.

In case of "profile02", KickstartFileSyncTask will create the following file:

      /var/lib/rhn/kickstarts/wizzard/profile02.cfg

but will never tell cobbler back that the path to the kickstart file has
changed.

Next time KickstartFileSyncTask will run, it will do the same procedure
for "profile02" again.