Description of problem: In both current scl pg 9.5 and scl pg 10 (copying from engine-setup logs): 2019-02-17 02:47:42,455-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.provisioning.postgres plugin.execute:926 execute-output: ('/opt/rh/rh-postgresql95/root/usr/bin/postgresql-setup', 'initdb') stderr: WARNING: using obsoleted argument syntax, try --help WARNING: arguments transformed to: postgresql-setup --initdb --unit rh-postgresql95-postgresql * Initializing database in '/var/opt/rh/rh-postgresql95/lib/pgsql/data' * Initialized, logs are in /var/lib/pgsql/initdb_rh-postgresql95-postgresql.log 2019-02-03 12:26:35,558+0200 DEBUG otopi.plugins.ovirt_engine_setup.cinderlib.provisioning.postgres plugin.execute:926 execute-output: ('/opt/rh/rh-postgresql10/root/usr/bin/postgresql-setup', 'initdb') stderr: WARNING: using obsoleted argument syntax, try --help WARNING: arguments transformed to: postgresql-setup --initdb --unit rh-postgresql10-postgresql * Initializing database in '/var/opt/rh/rh-postgresql10/lib/pgsql/data' * Initialized, logs are in /var/lib/pgsql/initdb_rh-postgresql10-postgresql.log Version-Release number of selected component (if applicable): Current scl pg (affects both 4.2 and 4.3/master) How reproducible: Always Steps to Reproduce: 1. install and setup engine on clean machine 2. 3. Actual results: Warning above Expected results: No warning Additional info: Need to check when 'initdb' is going to be removed - then, current bug will be more urgent, better prepare beforehand...
Seems like the message was added almost 5 years ago [1], perhaps it's enough to fix in 4.3. [1] https://github.com/devexp-db/postgresql-setup/commit/1a206187ca761c75e13989eab92430df689e1eca
(In reply to Yedidyah Bar David from comment #1) > Seems like the message was added almost 5 years ago [1], perhaps it's enough > to fix in 4.3. > > [1] > https://github.com/devexp-db/postgresql-setup/commit/ > 1a206187ca761c75e13989eab92430df689e1eca I agree, I'd fix only in 4.3
No initdb obsolete warning in setup log for engine and also separate dwh. Installation successful. verified in ovirt-engine-setup-4.3.2-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.2 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.