Bug 1085364 - rhevm-reports-setup fails if pg_hba.conf is manually modified
Summary: rhevm-reports-setup fails if pg_hba.conf is manually modified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Yedidyah Bar David
QA Contact: Barak Dagan
URL:
Whiteboard: integration
Depends On: 1079903 1084760
Blocks: 1085374
TreeView+ depends on / blocked
 
Reported: 2014-04-08 12:59 UTC by Yedidyah Bar David
Modified: 2014-06-09 15:28 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, rhevm-reports-setup failed if the default spacing of pg_hba.conf was manually modified. Now, the command does not check exact spacing in the file, and setup completes successfully.
Clone Of: 1084760
: 1085374 (view as bug list)
Environment:
Last Closed: 2014-06-09 15:28:21 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0602 0 normal SHIPPED_LIVE rhevm-reports 3.4 bug fix and enhancement update 2014-06-09 19:26:10 UTC
oVirt gerrit 26528 0 None None None Never
oVirt gerrit 26529 0 None None None Never

Comment 2 Yaniv Lavi 2014-04-08 13:28:43 UTC 
Should be fixed in otopi, please test.



Yaniv
Comment 3 Barak Dagan 2014-04-28 11:12:20 UTC 
Verified on av6.1:


rhevm-3.4.0-0.13.beta3.el6ev.noarch
rhevm-dwh-3.4.0-6.el6ev.noarch
rhevm-reports-3.3.2-3.el6ev.noarch
jasperreports-server-pro-5.5.0-6.el6ev.noarch


# "local" is for Unix domain socket connections only
local    all          all                                md5
host    rhevmreports    engine_reports  0.0.0.0/0               md5

changed ident to md5 i 1st raw and added an extra space between each pair.
Comment 4 errata-xmlrpc 2014-06-09 15:28:21 UTC 
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/RHEA-2014-0602.html
Note You need to log in before you can comment on or make changes to this bug.