Bug 1054667
| Summary: | [rhevm-reports-setup] (remote install) avoid hard-code DB name by allowing the user to define it | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
| Component: | ovirt-engine-reports | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED ERRATA | QA Contact: | movciari |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.3.0 | CC: | dfediuck, didi, gklein, iheim, juwu, movciari, rbalakri, Rhev-m-bugs, sherold, talayan, yeylon, ylavi |
| Target Milestone: | --- | ||
| Target Release: | 3.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In Red Hat Enterprise Virtualization versions prior to 3.4, the database name was hardcoded and it was not possible to specify a different database name. With this update, the reports setup utility was replaced with a plug-in to use with the common engine-setup utility, and this plug-in queries all database credentials. This feature was considered as a tech preview feature in Red Hat Enterprise Virtualization 3.4 and is now a supported feature.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-11 18:16:49 UTC | Type: | Bug |
| 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: | 1142923, 1156165 | ||
|
Description
Jiri Belka
2014-01-17 08:52:42 UTC
This bug affects only 3.3. In 3.4+ we do ask for everything. Not sure we should really solve it for 3.3 at this point in time. should be in the code of first release. Please test once it's out. Yaniv Hi didi, I have updated the doc text. Please let me know if this is correct or not. Cheers, Julie Looks good to me. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0176.html |