Bug 1065781
| Summary: | [rhevm-dwh-setup] rhevm-dwh-setup drops '"' from read db password | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine-dwh | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aberezin, acathrow, adahms, alonbl, bazulay, didi, gklein, iheim, jbelka, pstehlik, Rhev-m-bugs, sbonazzo, scohen, yeylon, ylavi |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | is35 - rhevm-dwh-3.3.2-1.el6ev.noarch.rpm | Doc Type: | Bug Fix |
| Doc Text: |
Previously, including a double quotation mark in the password for the history database would cause the rhevm-dwh-setup command to fail due to an authentication error. This was caused by the double quotation marks not being considered a part of the password. Now, the rhevm-dwh-setup command disallows the characters '"', '\', '#', and '$'.
|
Story Points: | --- |
| Clone Of: | 1052202 | Environment: | |
| Last Closed: | 2014-04-09 17:42:52 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: | 1052202 | ||
| Bug Blocks: | |||
|
Comment 2
Yedidyah Bar David
2014-03-05 14:13:55 UTC
Your comment #2 seems be wrong. # rhevm-dwh-setup Welcome to ovirt-engine-dwh setup utility In order to proceed the installer must stop the ovirt-engine service Would you like to stop the ovirt-engine service (yes|no): yes Stopping ovirt-engine... [ DONE ] Remote installation is selected. Remote installation selected. Make sure that DBA creates a user and the database in the following fashion: create role <role> with login encrypted password <password>; create database ovirt_engine_history template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8' owner <role>; Database user [engine_history]: remote_history Database password: Password must not contain ["] Database password: Error encountered while installing rhevm-dwh, please consult the log file: /var/log/ovirt-engine/rhevm-dwh-setup-2014_03_21_10_52_52.log [root@testovic ~]# rpm -q rhevm-dwh rhevm-dwh-3.3.2-1.el6ev.noarch Incorrectly understood the issue, it is about loading engine's DB password, not about rhevm-dwh-setup not accepting '"' or '$' as dwh remote DB password. ok, rhevm-dwh-3.3.2-1.el6ev.noarch (In reply to Jiri Belka from comment #4) > Incorrectly understood the issue, it is about loading engine's DB password, > not about rhevm-dwh-setup not accepting '"' or '$' as dwh remote DB password. Indeed. The fix might solve also the issue that we "fixed" by preventing special chars in dwh db user password, but I didn't test that and didn't remove the code forbidding it. You can trivially verify if it's also solved by changing INVALID_PASSWORD_CHARS (around line 70 of dwh-setup) to '' and trying all relevant flows. This bug is currently attached to errata RHBA-2014:17206 If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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. http://rhn.redhat.com/errata/RHBA-2014-0386.html Closing old needinfo's. |