As a part of automatic upgrade from RH SCL 3.2 to RH SCL 3.4 PostgreSQL 10 will receive an upgrade from 10.6 to 10.12. So we need to verify all upgrade scenarios (local & remote engine & DWH database) to see if there are any manual steps needed (which we would need to document) or everything is automatic and just RPM upgrade is enough. This is 4.3.z only change.
upgrade SCL 10.6 to SCL 10.12 ================================= **************************************************************** Tested with 1 NFS master SD / 1 running host/ 1 running VM with 1 Disk and 1 Nic **************************************************************** For local engine/dwh , all you have to do ========================================= 1) yum install -y centos-release-scl-rh 2) yum --enablerepo=centos-sclo-rh-testing install rh-postgresql10-postgresql-server 3) scl enable rh-postgresql10 bash 4) engine-setup After engine-setup completes, the engine was running with SD/Host/VM as before the upgrade. For remote engine/DWH ====================== **************************************************************** Tested with backup/restore mode when backup is done with PG 10.6 and restore is done on PG 10.12 using engine-backup **************************************************************** This also worked smoothly without any problems, engine after restore followed by engine-setup runs with SD/Host/VM as before the restore. The upgrade from PG 10.6 to 10.12 is safe and basically is only a RPM upgrade
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3.z': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3.z': '?'}', ] For more info please contact: rhv-devops
local engine&dwh db - OK remote engine&dwh db - just update postgres packages, OK No additional manual steps needed, verified in updating ovirt-engine-4.3.9.4-11.el7.noarch -> ovirt-engine-4.3.10.3-0.1.master.el7.noarch
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-2020:2396