Bug 584600

Description of problem:
Customer deletes a few ks profiles and then finds himself no longer able to use provisioning functionality b/c cobblerd fails to start with error message "invalid profile name (<name-of-profile-he-just-deleted>)". cobbler commands such as "cobbler report" and "cobbler profile list" returns same error. The profile was deleted successfully, and is not in /var/lib/cobbler/config/profiles.d/ nor is it in rhnKsData in database.  It turns out that one of the system configs in /var/lib/cobbler/config/systems.d/ still has a reference to the deleted profile, and fixing that manually brought back cobbler/kickstart functionality.  We're not sure how that happened since cobbler system list does not show this system, so that itself is problematic, however cobbler should handle this better:

There're 3 parts to this bug -
1. possible incomplete deletion of cobbler profile such that not all system configs referring to profile are removed, and/or incomplete deletion of system configs (have not been able to reproduce this, so not certain, unlike parts 2 & 3 below);
2. need better error message - instead of just saying "invalid profile name", it should tell the user where the error is occuring, for example "unable to find profile xyz used by system abc".
3. need better error-handling - just b/c one config file has issues should not cause the entire cobbler/provisioning functionality to crash down, it needs to report the error and allow the rest of the kickstart functinality to remain working. 

Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.3.0

System architecture(s):
arch=x86_64
release=5
flavor=server
base=rhel-x86_64-server-5

How reproducible:
Always.

Steps to Reproduce:
1. 5.3 Satellite with >=2 ks profiles with some system configs.
2. delete one of the profiles, however leave one of the configs still referring to the deleted profile in "profile"
3. try to provision systems, restart cobblerd, and/or do "cobbler profile list" etc..

Actual results:
See above.

Expected results:
See parts 2 & 3 above.

Additional info: