+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1611617 +++ ====================================================================== Description of problem: Upgrade aborts with "ERROR: must be owner of extension plpgsql during Restoring DWH database ovirt_engine_history" Version-Release number of selected component (if applicable): 4.2.4/4.2.5 How reproducible: 100% in my environment Steps to Reproduce: 1. engine-setup 2. Take defaults for all except add full vacuum Actual results: ERROR: must be owner of extension plpgsql during Restoring DWH database ovirt_engine_history Expected results: Successful upgrade Additional info: (Originally by Thom Carlin)
Eli, can you please look into this? (Originally by Sandro Bonazzola)
1. The bug is about errors from pg_restore, which is ran during _rollback_. So to reproduce, you have to cause engine-setup to fail somehow (bug 1609839, in this case, but can be anything). 2. engine-setup already filters out some errors from pg_restore, which we decided are harmless. These are logged but are not shown to the user. 3. Unfiltered errors are also shown to the user, and it's up to the user to decide if that's a problem or not. Other than that, it continues as usual. So if the user decided that the errors are harmless, nothing else needs to be done (other than handling the original cause for rollback and then trying to upgrade again). 4. In this case, the unfiltered errors are: otopi.ovirt_engine_setup.engine_common.database database.restore:942 Errors unfiltered during restore: pg_restore: [archiver (db)] Error from TOC entry 7310; 0 0 COMMENT EXTENSION "uuid-ossp" pg_restore: [archiver (db)] could not execute query: ERROR: must be owner of extension uuid-ossp 5. I am pretty certain that they are harmless. Also pushed a patch (93544) to add them to the filtered errors. If Eli agrees, that's enough. 6. Also, since they seem harmless to me, lowered priority/severity accordingly. 7. Also changing the summary line according to (1.) and (4.). uuid-ossp was introduced in bug 1515635, 4.2.1. (Originally by didi)
I aborted engine-setup with otopi-debug-plugins OTOPI_FORCE_FAIL_STAGE=STAGE_MISC OTOPI_FORCE_FAIL_PRIORITY=PRIORITY_LOW engine-setup And log doesn't contain error as in previous version ERROR: must be owner of extension uuid-ossp but it still fails and log contains 2018-08-13 13:48:31,593+0200 ERROR otopi.ovirt_engine_setup.engine_common.database database.restore:945 Errors while restoring engine database, please check the log file for details 2018-08-13 13:27:36,714+0200 DEBUG otopi.ovirt_engine_setup.engine_common.database database.restore:950 Errors unfiltered during restore: pg_restore: [archiver (db)] Error from TOC entry 7264; 0 0 COMMENT EXTENSION "uuid-ossp" tested in ovirt-engine-setup-plugin-ovirt-engine-common-4.2.5.3-0.1.el7ev.noarch
rollback was successfull verified in ovirt-engine-setup-plugin-ovirt-engine-common-4.2.5.4-0.1.el7ev.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-2018:2541