Bug 701408 - installer ignores rhq-server.properties' type-mapping, always defaults to postgres
Summary: installer ignores rhq-server.properties' type-mapping, always defaults to pos...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Installer
Version: 4.0.0.Beta2
Hardware: All
OS: All
medium
medium vote
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-02 19:59 UTC by Mike Foley
Modified: 2022-03-31 04:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.