Description of problem:
We want to know if we can't power on or reboot a system when scheduling a job, but I'm not sure we really care if we can't power off a system.
We ran into a problem where we couldn't abort or cancel a recipe in beaker because cobbler was mis-behaving. We eventually fixed cobbler so it could be aborted but we shouldn't get stuck in a loop because of a bug in cobbler.
Version-Release number of selected component (if applicable):
Put a bad profile on a system in cobbler
*** Bug 725620 has been marked as a duplicate of this bug. ***