Bug 1463303

Summary:	[TEXT] Unclear installation on setting up variables on remote database
Product:	[oVirt] ovirt-engine	Reporter:	Lukas Svaty <lsvaty>
Component:	Setup.Core	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.1.3.3	CC:	amureini, bugs, lsvaty, rgolan
Target Milestone:	ovirt-4.3.0	Keywords:	EasyFix
Target Release:	---	Flags:	ylavi: ovirt-4.3+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:46:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Svaty 2017-06-20 14:23:59 UTC

Description of problem:
Unclear installation on setting up variables on remote database

[ ERROR ] Please set:  autovacuum_vacuum_scale_factor = 0.01  autovacuum_analyze_scale_factor = 0.075  autovacuum_max_workers = 6  maintenance_work_mem = 65536  max_connections = 150 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .


what does the "on 'None'" means?

Version-Release number of selected component (if applicable):
ovirt-engine-setup-4.1.3.4-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. run ovirt-engine and try to install on remote database
Actual results:
[ ERROR ] Please set:  autovacuum_vacuum_scale_factor = 0.01  autovacuum_analyze_scale_factor = 0.075  autovacuum_max_workers = 6  maintenance_work_mem = 65536  max_connections = 150 in postgresql.conf on 'None'. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .

Expected results:
[ ERROR ] Please set:  autovacuum_vacuum_scale_factor = 0.01  autovacuum_analyze_scale_factor = 0.075  autovacuum_max_workers = 6  maintenance_work_mem = 65536  max_connections = 150 in postgresql.conf. Its location is usually /var/lib/pgsql/data , or somewhere under /etc/postgresql* .

Comment 1 Sandro Bonazzola 2017-06-21 06:35:23 UTC

Roy, can you please have a look? Is it this related to your vacuum changes?

Comment 2 Roy Golan 2017-06-25 12:34:39 UTC

Those are the rough edges around remote installation of DB.
The "None" should have been the name of the machine hosting the db. If this installation would run locally it should yield 'localhost' I think 

It might be related to vacuum changes or might always been missing in db only installations.

Comment 3 Yaniv Lavi 2018-06-25 07:57:52 UTC

*** Bug 1543329 has been marked as a duplicate of this bug. ***

Comment 4 Sandro Bonazzola 2018-12-03 08:49:17 UTC

Almost all of this should be already fixed, moving to QE.

Comment 5 Lucie Leistnerova 2018-12-11 18:33:17 UTC

Message looks fine (for both dwh and engine remote database)

         Please note the following required changes in postgresql.conf on 'remotedb.redhat.com':
           'autovacuum_vacuum_scale_factor' is currently '0.2'. It is required to be at most '0.01'.
...
         postgresql.conf is usually in /var/lib/pgsql/data, /var/opt/rh/rh-postgresql10/lib/pgsql/data, or somewhere under /etc/postgresql* . You have to restart PostgreSQL after making these changes.

verified in ovirt-engine-setup-4.3.0-0.6.alpha2.el7.noarch

Comment 6 Yedidyah Bar David 2018-12-12 09:09:50 UTC

I think I fixed everything in the scope of bug 1578276. Feel free to close as duplicate.

Lukas (asking you as reporter, I realize you opened it a long time ago): Anything missing? Thanks.

Comment 7 Lukas Svaty 2018-12-19 15:28:35 UTC

seems to by lucies comment that hostname of remote db server is correctly filled, kudos to didi and lucie :)

Comment 8 Sandro Bonazzola 2019-02-13 07:46:45 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.