|Summary:||installer doesn't tell me the db schema exists|
|Product:||[Other] RHQ Project||Reporter:||John Mazzitelli <mazz>|
|Component:||Installer||Assignee:||RHQ Project Maintainer <rhq-maint>|
|Status:||CLOSED NOTABUG||QA Contact:||Corey Welton <cwelton>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-02-17 17:47:24 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description John Mazzitelli 2010-06-03 19:54:09 UTC
Description of problem: Upgrading from a previous version, and pointing the installer to the default DB settings, the installer didn't tell me that the db schema exists (and thus doesn't give me the drop down menu to pick if I want to overwrite or keep nor the drop down menu to say if this is a new server or an existing registered server. The only way for me to get them is to explicitly click the Test Connection button. How reproducible: Install an old version of the server, get it running (I used the default postgres settings that come out of box - postgres on localhost, rhq database name and rhqadmin/rhqadmin as the credentials). Then shut it down, and install the new version. Go to the installer and see that you aren't told that the schema already exists nor can you tell you if you want this to be a new server or register it as one of the alerady existing ones. Then click the Test Connection button (without touching anything else) and see you get the drop down menus.
Comment 1 Charles Crouch 2010-07-06 23:59:09 UTC
So what changed from 2.3.1? This would only have ever work for databases using the default username and password correct? Perhaps we just need an extra line in the UI saying "Please hit the Test Connection button to determine if you already an existing db schema at this location". The key thing to avoid is allowing people to overwrite existing schemas unwittingly.
Comment 2 John Mazzitelli 2010-07-09 16:08:24 UTC
this might not be a problem - I need to go back and check. Its possible that I wasn't connected to the database with the correct password and thus wasn't able to see the DB schema.
Comment 3 John Mazzitelli 2010-07-09 16:12:19 UTC
yeah, ok, this isn't a problem. At the most, we could do charles' suggestion, "an extra line in the UI saying "Please hit the Test Connection button to determine if you already an existing db schema at this location". lowering priority since this appears to be a minor annoyance.