Description of problem: The procedure described in "https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/data_warehouse_guide/allowing_read_only_access_to_the_history_database" is incomplete and do not allow the user to effectively connect to the database How reproducible: Always Steps to Reproduce: 1. Follow step by step the guide Actual results: User try to connect to the db using the new [user name] created, and get the error: -bash-4.2$ psql -U [user name] ovirt_engine_history psql: FATAL: Peer authentication failed for user "tudwhro" Expected results: Being able to connect Additional info: The missing parts in the document are 2: a) For the new user to be able to access the DB you still need to configure the authentication method in the pg_hba.conf file: /var/lib/pgsql/data/pg_hba.conf ~~~ # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all peer host ovirt_engine_history ovirt_engine_history 0.0.0.0/0 md5 host ovirt_engine_history ovirt_engine_history ::0/0 md5 host ovirt_engine_history $RO_USER 0.0.0.0/0 md5 host ovirt_engine_history $RO_USER ::0/0 md5 host engine engine 0.0.0.0/0 md5 host engine engine ::0/0 md5 # IPv4 local connections: host all all 127.0.0.1/32 ident # IPv6 local connections: host all all ::1/128 ident ~~~ Replace $RO_USER with the corresponding name, reload postgresql service (systemctl reload postgresql), b) show an example of communication string, specifying that also from the manager will be requested to express the host variable. To query the DB do always express via the -h flag the host variable as localhost for the md5 method to be discovered while accessing the DB # psql -h localhost -U $RO_USER ovirt_engine_history
*** This bug has been marked as a duplicate of bug 1488178 ***