Red Hat Bugzilla – Bug 484264
Internal Server Error when modifying a cloned kickstart/No boot menu entry
Last modified: 2009-09-10 08:05:16 EDT
Created attachment 331042 [details]
Description of problem:
I have my activation key set up to allow config file deployment, but the client always bombs out with "Local permission not set for action type configfiles.deploy".
When I try to turn on the checkbox on the kickstart profile itself, it always reverts back to cleared. I've tried adding "rhn-actions-control --enable-all" to my post-script, but that's a no-go.
furthermore, when I clone an existing kickstart profile, the resulting profile does not show up in the boot menu.. and editing Kickstart Details/Operating System on that results in a 500.. null pointer exception.
Error is attached.
After restarting taskomatic, these entries were written to /var/log/rhn/rhn_taskomatic_daemon.log
13:05:02 | 2009-02-05 13:05:02,691 [DefaultQuartzScheduler_Worker-9] WARN com.redhat.rhn.manager.kickstart.cobbler.CobblerProfileCommand - We could not find a default kickstart session for this ksdata: Production_App_Php5
INFO | jvm 1 | 2009/02/05 13:05:03 | 2009-02-05 13:05:03,192 [DefaultQuartzScheduler_Worker-9] WARN com.redhat.rhn.manager.kickstart.cobbler.CobblerProfileCommand - We could not find a default kickstart session for this ksdata: ClonedTest
After restarting taskomatic, the profile is now listed in "cobbler sync profile" and the gui appears to work as expected.
make sure that in the activation key -> packages
the following packages are listed.
Also, make sure that the provisioning entitlement is enabled for that activation key.
The three packages, and provisioning entitlement should get set automatically when you check the box "enable config file deployment", however if that is NOT happening.. thats a bug.
These issues should be fixed now:
1. SHould be able to enable config deploy on a kickstart profile.
2. The kickstart cloning oddness, should be fixed now. Moving to on_qa for more testing.
Spacewalk 0.6 released