Bug 863479 - KickstartFileSyncTask will be repeated endlessly for kickstart profiles renamed before upgrade to Satellite 5.5
KickstartFileSyncTask will be repeated endlessly for kickstart profiles renam...
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomas Lestach
Pavel Studeník
: 862144 (view as bug list)
Depends On:
Blocks: 819027
  Show dependency treegraph
Reported: 2012-10-05 10:59 EDT by Milan Zazrivec
Modified: 2013-01-07 23:06 EST (History)
7 users (show)

See Also:
Fixed In Version: spacewalk-java-1.7.54-103
Doc Type: Bug Fix
Doc Text:
Consequence: Any kickstart profile rename on RHN Satellite 5.4 causes issues after Satellite upgrade to 5.5. The profile is unusable and any tries to sync the profile fail with a 'kickstart not found' exception and get repeated endlessly Result: Renamed kickstart profiles get properly synced to cobbler.
Story Points: ---
Clone Of:
Last Closed: 2012-10-23 02:38:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Zazrivec 2012-10-05 10:59:01 EDT
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):

How reproducible:

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


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


5. cobbler's record will remain unchanged

During the upgrade to Satellite 5.5, content of


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

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


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

Next time KickstartFileSyncTask will run, it will do the same procedure
for "profile02" again.
Comment 1 Tomas Lestach 2012-10-08 08:00:12 EDT
There's a need to update also cobbler profile configuration ... enhancing ks file sync ...

spacewalk.git: 1c7490e39d859179573e2c735e82bc3acb8e3f05
Comment 6 errata-xmlrpc 2012-10-23 02:38:31 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

Comment 7 Pavel Studeník 2012-10-24 09:37:26 EDT
*** Bug 862144 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.