Bug 599733
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> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.0.0 | ||
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: | 2011-02-17 17:47:24 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: | 585306 |
Description
John Mazzitelli
2010-06-03 19:54: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. 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. 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. |