Bug 1039747
| Summary: | rhevm-log-collector does not collect database dump | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Derrick Ornelas <dornelas> |
| Component: | ovirt-engine-log-collector | Assignee: | Sandro Bonazzola <sbonazzo> |
| Status: | CLOSED ERRATA | QA Contact: | DuĊĦan Kajan <dkajan> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | acathrow, alonbl, didi, emesika, iheim, knesenko, lyarwood, myakove, pstehlik, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | EasyFix |
| Target Release: | 3.3.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | integration | ||
| Fixed In Version: | rhevm-log-collector-3.3.1-5.el6ev | Doc Type: | Bug Fix |
| Doc Text: |
Previously it was possible to access the database through a UNIX socket as the PostgreSQL sosreport plugin did not handle identity authentication correctly. As a result, the rhevm-log-collector did not correctly gather an engine database dump. Now the access for the 'engine' user is limited to TCP connections, and the rhevm-log-collector always uses the database host.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-21 17:01:12 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: | 1020228 | ||
|
Description
Derrick Ornelas
2013-12-09 21:55:38 UTC
# PGPASSWORD="QjytYXZa" pg_dump -C -U engine -w -f /tmp/blah.tar -F t engine pg_dump: [archiver (db)] connection to database "engine" failed: FATAL: Ident authentication failed for user "engine" # PGPASSWORD="QjytYXZa" pg_dump -C -h localhost -U engine -w -f /tmp/blah.tar -F t engine # file /tmp/blah.tar /tmp/blah.tar: tar archive I guess this can be fixed in a number of ways, but it appears that the simpliest is for log-collector to pass "postgresql.dbhost=localhost" to sosreport if '--pg-dbhost' isn't explicitly set, which is supposed to be the default anyways # /usr/sbin/sosreport --batch --report -o postgresql --tmp-dir=/tmp/logcollector-zlIcO8/log-collector-data -k postgresql.dbname=engine -k postgresql.username=engine -k postgresql.password=QjytYXZa -k postgresql.dbhost=localhost sosreport (version 2.2) This command will collect diagnostic and configuration information from this Red Hat Enterprise Linux system and installed applications. An archive containing the collected information will be generated in /tmp/logcollector-zlIcO8/log-collector-data and may be provided to a Red Hat support representative. Any information provided to Red Hat will be treated in accordance with the published support policies at: https://access.redhat.com/support/ The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Running plugins. Please wait ... Completed [1/1] ... Creating compressed archive... Your sosreport has been generated and saved in: /tmp/logcollector-zlIcO8/log-collector-data/sosreport-rhn-support-dornelas-20131209170655-7d28.tar.xz The md5sum is: bd81db9cc40f1ccd7be6d27ebc827d28 Please send this file to your support representative. # tar xf /tmp/logcollector-zlIcO8/log-collector-data/sosreport-rhn-support-dornelas-20131209170536-fa49.tar.xz # file rhevdm33-2013120917051386626734/tmp/tmp8wkdEx/sos_pgdump.tar rhevdm33-2013120917051386626734/tmp/tmp8wkdEx/sos_pgdump.tar: tar archive Proposing this as blocker. Previously it was possible to access the database through unix socket. Now the access for user engine is limited to tcp connection. log-collector just used socket if db host was localhost. The fix on log-collector side is just always use db host, also if it's localhost. Merged on upstream master and 3.3 branches. rhevm-3.3.0-0.41.el6ev.noarch 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-0039.html |