Red Hat Bugzilla – Bug 1592286
[downstream clone - 4.2.4] engine-setup upgrade to PG 9.5 fails with umask 0077
Last modified: 2018-06-27 06:05:05 EDT
+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1588431 +++ ====================================================================== Description of problem: While upgrading from 4.1.11 to 4.2.3 seeing below errors, ~~~ connection to database failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/lib/pgsql/.s.PGSQL.5432"? could not connect to old postmaster started with the command: "/usr/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/lib/pgsql/data" -o "-p 5432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/lib/pgsql'" start Failure, exiting [root@sldohd2trhm0500 /]# rpm -qa | grep ovirt-engine ovirt-engine-dwh-4.1.9-1.el7ev.noarch ovirt-engine-restapi-4.1.11.2-0.1.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.2.3.8-0.1.el7.noarch ovirt-engine-4.1.11.2-0.1.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-engine-tools-backup-4.1.11.2-0.1.el7.noarch ovirt-engine-dwh-setup-4.2.2.2-1.el7ev.noarch ovirt-engine-extension-aaa-jdbc-1.1.6-1.el7ev.noarch ovirt-engine-cli-3.6.8.1-1.el7ev.noarch ovirt-engine-extension-aaa-misc-1.0.1-3.el7ev.noarch ovirt-engine-extension-aaa-ldap-1.3.7-1.el7ev.noarch ovirt-engine-extensions-api-impl-4.1.11.2-0.1.el7.noarch ovirt-engine-backend-4.1.11.2-0.1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.2.3.8-0.1.el7.noarch ovirt-engine-userportal-4.1.11.2-0.1.el7.noarch ovirt-engine-setup-4.2.3.8-0.1.el7.noarch ovirt-engine-websocket-proxy-4.1.11.2-0.1.el7.noarch ovirt-engine-dbscripts-4.1.11.2-0.1.el7.noarch ovirt-engine-lib-4.2.3.8-0.1.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.7-1.el7ev.noarch ovirt-engine-dashboard-1.1.8-1.el7ev.noarch ovirt-engine-tools-4.1.11.2-0.1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.2.3.8-0.1.el7.noarch ovirt-engine-metrics-1.0.8-1.el7ev.noarch ovirt-engine-vmconsole-proxy-helper-4.1.11.2-0.1.el7.noarch ovirt-engine-setup-base-4.2.3.8-0.1.el7.noarch ovirt-engine-webadmin-portal-4.1.11.2-0.1.el7.noarch python-ovirt-engine-sdk4-4.1.7-1.el7ev.x86_64 ovirt-engine-setup-plugin-ovirt-engine-4.2.3.8-0.1.el7.noarch ~~~ Version-Release number of selected component (if applicable): RHV 4.1.11 (Originally by Shruti Kavishwar)
*** Bug 1588819 has been marked as a duplicate of this bug. *** (Originally by Sandro Bonazzola)
So I've created BZ1591802 to bump to latest SCL PG 9.5 in RHV 4.2.4. Do we plan to post some fixed or just bumping the PG version will solve this issue? (Originally by Martin Perina)
(In reply to Martin Perina from comment #12) > So I've created BZ1591802 to bump to latest SCL PG 9.5 in RHV 4.2.4. Do we > plan to post some fixed or just bumping the PG version will solve this issue? Bumping the PG version should solve, and should be enough, IMO. I didn't plan to push a patch, if the patch will not be included in a version earlier than what we can get with a newer PG. Since bug 1591802 looks good to be shipped in 4.2.4, I think it's enough. I am updating the bug accordingly to what we know now. CEE (Shruti/Sachin/Ulhas) - please revert my changes if 'umask 0022; engine-setup' does not work for you. Thanks. (Originally by didi)
QE: The flow to reproduce/verify current bug, as we currently know, is: 1. Install and setup 4.1 engine 2. Add 4.2 repos and update setup packages 3. umask 0077 4. engine-setup With a broken PG (9.5.9-1), it should fail with error above. With a fixed PG (9.5.9-4), it should succeed. (Originally by didi)
engine 4.1 successfully upgraded to 4.2.4 with umask 0077 verified in ovirt-engine-4.2.4.4-0.1.el7_3.noarch with rh-postgresql95-postgresql-9.5.9-4.el7.x86_64.rpm
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. https://access.redhat.com/errata/RHBA-2018:2081