Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1588431

Summary: engine-setup upgrade to PG 9.5 fails with umask 0077
Product: Red Hat Enterprise Virtualization Manager Reporter: Shruti <skavishw>
Component: rh-postgresql95Assignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.1.11CC: abpatil, didi, dmoppert, lsurette, mgoldboi, mperina, pmatyas, Rhev-m-bugs, schandle, skavishw, sraje, srevivo, usurse
Target Milestone: ovirt-4.3.0Keywords: TestOnly, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1592286 (view as bug list) Environment:
Last Closed: 2019-05-31 08:52:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1591802    
Bug Blocks: 1592286    

Description Shruti 2018-06-07 10:36:53 UTC
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

Comment 10 Sandro Bonazzola 2018-06-15 13:41:58 UTC
*** Bug 1588819 has been marked as a duplicate of this bug. ***

Comment 12 Martin Perina 2018-06-15 15:43:15 UTC
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?

Comment 13 Yedidyah Bar David 2018-06-17 06:49:39 UTC
(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.

Comment 14 Yedidyah Bar David 2018-06-17 06:52:43 UTC
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.

Comment 22 Lucie Leistnerova 2018-09-03 11:23:03 UTC
upgrade 4.1.9 -> 4.3 with umask 0077 was successful 

verified in ovirt-engine-4.3.0-0.0.master.20180902070649.gita860c9c.el7.noarch
with rh-postgresql95-postgresql-9.5.9-4.el7.x86_64.rpm

Comment 24 Sandro Bonazzola 2019-01-17 10:46:18 UTC
(In reply to Lucie Leistnerova from comment #22)
> upgrade 4.1.9 -> 4.3 with umask 0077 was successful 
> 
> verified in
> ovirt-engine-4.3.0-0.0.master.20180902070649.gita860c9c.el7.noarch
> with rh-postgresql95-postgresql-9.5.9-4.el7.x86_64.rpm

In 4.3 we are using postgresql 10, is this bug really relevant for 4.3?
Also direct upgrade from 4.1 to 4.3 is not supported.
Maybe we should close this as not a bug for 4.3?

Comment 25 Daniel Gur 2019-08-28 13:11:54 UTC
sync2jira

Comment 26 Daniel Gur 2019-08-28 13:16:07 UTC
sync2jira