Bug 701408

Summary:	installer ignores rhq-server.properties' type-mapping, always defaults to postgres
Product:	[Other] RHQ Project	Reporter:	Mike Foley <mfoley>
Component:	Installer	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0.0.Beta2	CC:	hrupp, mazz
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Foley 2011-05-02 19:59:13 UTC

Description of problem:
installer ignores rhq-server.properties' type-mapping, always defaults to postgres

Version-Release number of selected component (if applicable):
4.0

How reproducible:
100%

Steps to Reproduce:
1.  Upgrade of RHQ3 to RHQ4
2.
3.
  
Actual results:
installer defaults to postgres

Expected results:
installer defaults to previous setting as defined in rhq-server.properties


Additional info:

Comment 1 John Mazzitelli 2011-05-02 20:04:56 UTC

probably need to fix start.jsp. start looking in there for the possible problem.

fyi: the steps to reproduce in the description is not entirely accurate.

you don't even have to be doing an upgrade. Just, before you start a newly unzipped server distro, edit rhq-server.properties so that you change the db settings to, say, an oracle DB (you don't even need a real oracle db installed/running - you are just messing with the settings). When you start the server, the installer's db type drop down always defaults to postgres. flipping to oracle, changes all your custom settings to the defaults.