Red Hat Bugzilla – Bug 109900
MasterTool should detect conflicts before going through interactive setup
Last modified: 2007-04-18 12:59:25 EDT
Description of problem:
MasterTool should detect conflicts before going through interactive
setup. Currently if I run "ccm load --interactive ccm-core" after I've
already loaded core, I don't get any error messages until after I've
gone through the interactive loader/config parameter setting stage.
If I've already loaded some of the apps, or dependency information
isn't met, etc., I should be informed of it _before_ I go thorugh the
trouble of configuring parameters.
In addition, the error message should tell me which app is causing the
conflict. "conflicting tables acs_objects" isn't very descriptive.
Steps to Reproduce:
1.ccm load --interactive ccm-core
2.do it again