Bug 109900

Summary:	MasterTool should detect conflicts before going through interactive setup
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Scott Seago <sseago>
Component:	installation	Assignee:	ccm-bugs-list
Status:	CLOSED WONTFIX	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	nightly	CC:	bstein
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-03-09 15:36:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	110923, 111508

Description Scott Seago 2003-11-12 19:47:36 UTC

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.



How reproducible:
always

Steps to Reproduce:
1.ccm load --interactive ccm-core
2.do it again
3.