Description of problem: As a part of BZ1515635 we have added a required for uuid-ossp PostgreSQL extension to be present in engine database. For databases managed by engine-setup this is performed automatically, but non-managed databases (usually remote databases) this is needs to be done manually by administrators. We need to add following steps: New installation: 1. Requirement to install rh-postgresql95-postgresql-contrib package on remote database host 2. Once database is created administrators need to add uuid-ossp extension to it using: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" postgres=# CREATE EXTENSION "uuid-ossp";; Upgrade: 1. Requirement to install rh-postgresql95-postgresql-contrib package on remote database host 2. Once database is upgraded to 9.5 administrators need to remove our custom implementation and add uuid-ossp extension to it using: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1();; postgres=# CREATE EXTENSION "uuid-ossp"; Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
- Do we need it before upgrade of RHV Manager? (do we assume the external DB is upgraded before? During?) - Can we provide a normal check for this, so users will not it's not correctly installed? - Any chance for an Ansible playbook to do it?
(In reply to Yaniv Kaul from comment #1) > - Do we need it before upgrade of RHV Manager? (do we assume the external DB > is upgraded before? During?) See also bug 1498351. > - Can we provide a normal check for this, so users will not it's not > correctly installed? We do, and want to improve it, see also bug 1534913. > - Any chance for an Ansible playbook to do it?
(In reply to Yaniv Kaul from comment #1) > - Do we need it before upgrade of RHV Manager? (do we assume the external DB > is upgraded before? During?) AFAIK the correct steps for upgrade are: 1. Stop the engine 2. Add repos if needed and upgrade 'engine*setup*' packages 3. Upgrade remote db from PG 9.2 to SCL PG 9.5 (including installing uuid-ossp extension as this bug covers) 4. Execute engine-setup to perform engine upgrade > - Can we provide a normal check for this, so users will not it's not > correctly installed? Well right now if uuid-ossp extension is not installed we will detect that during engine-setup part and failed the upgrade. We have opened BZ1498351 to try to detect that in early stages of engine-setup before we actually started to do the upgrade, so we will not need to perform rollback of engine-setup upgrade. > - Any chance for an Ansible playbook to do it? AFAIK docs team is already working on Upgrade Guide to specify database upgrade steps which similar to new remote db installation [1]. So yes, in theory we should be able to create an Ansible playbook to perform all those steps. Although I'd expect that users with remote db did that on purpose and they have experiences with managing PostgreSQL database, so not how useful would be that playbook for them comparing to detailed steps in upgrade guide. [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html/installation_guide/appe-preparing_a_remote_postgresql_database_for_use_with_the_red_hat_enterprise_virtualization_manager
(In reply to Martin Perina from comment #0) > Description of problem: > > As a part of BZ1515635 we have added a required for uuid-ossp PostgreSQL > extension to be present in engine database. For databases managed by > engine-setup this is performed automatically, but non-managed databases > (usually remote databases) this is needs to be done manually by > administrators. > > We need to add following steps: > > New installation: > 1. Requirement to install rh-postgresql95-postgresql-contrib package > on remote database host > 2. Once database is created administrators need to add uuid-ossp extension > to it using: > su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" > postgres=# CREATE EXTENSION "uuid-ossp";; Correction: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine" postgres=# CREATE EXTENSION "uuid-ossp"; > > Upgrade: > 1. Requirement to install rh-postgresql95-postgresql-contrib package > on remote database host > 2. Once database is upgraded to 9.5 administrators need to remove our > custom implementation and add uuid-ossp extension > to it using: > su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" > postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1();; > postgres=# CREATE EXTENSION "uuid-ossp"; Correction: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine" postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1(); postgres=# CREATE EXTENSION "uuid-ossp"; In both above examples "engine" specified using "-d" option is the name of engine database
(In reply to Martin Perina from comment #0) > Description of problem: > > As a part of BZ1515635 we have added a required for uuid-ossp PostgreSQL > extension to be present in engine database. For databases managed by > engine-setup this is performed automatically, but non-managed databases > (usually remote databases) this is needs to be done manually by > administrators. > > We need to add following steps: > > New installation: > 1. Requirement to install rh-postgresql95-postgresql-contrib package > on remote database host > 2. Once database is created administrators need to add uuid-ossp extension > to it using: > su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" > postgres=# CREATE EXTENSION "uuid-ossp";; Correction: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine" postgres=# CREATE EXTENSION "uuid-ossp"; > > Upgrade: > 1. Requirement to install rh-postgresql95-postgresql-contrib package > on remote database host > 2. Once database is upgraded to 9.5 administrators need to remove our > custom implementation and add uuid-ossp extension > to it using: > su - postgres -c "scl enable rh-postgresql95 -- psql -d engine_test" > postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1(); > postgres=# CREATE EXTENSION "uuid-ossp"; Correction: su - postgres -c "scl enable rh-postgresql95 -- psql -d engine" postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1(); postgres=# CREATE EXTENSION "uuid-ossp"; In both above examples "engine" specified using "-d" option is the name of engine database
*** Bug 1538250 has been marked as a duplicate of this bug. ***
I did my own 4.1 -> 4.2 upgrade with remote db, see https://bugzilla.redhat.com/show_bug.cgi?id=1498351#c12
I agree we can close current bug if we make sure we do not forget about uuid-ossp in bug 1498351. We opened that one before current, and didn't mention uuid-ossp in the description, so it might be better to keep both open just to not forget, or maintain somewhere else a checklist of subjects to be handled there.
(In reply to Yedidyah Bar David from comment #10) > I agree we can close current bug if we make sure we do not forget about > uuid-ossp in bug 1498351. We opened that one before current, and didn't > mention uuid-ossp in the description, so it might be better to keep both > open just to not forget, or maintain somewhere else a checklist of subjects > to be handled there. Thanks, Didi. To confirm, are you suggesting that there is no work to do in this bug? I had thought to use it for updates to the installation procedure, which we could release ASAP, since this bug seems to affect install and upgrade, and upgrade is waiting until GA. Is that still the case?
Sorry, you are right. Current bug affects both new install and upgrades.
Moving to ON_QA
Reviewed, all OK.
This content has been published to: - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html-single/installation_guide/#appe-Preparing_a_Remote_PostgreSQL_Database_for_Use_with_the_Red_Hat_Enterprise_Virtualization_Manager - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2-beta/html-single/installation_guide/#appe-Preparing_a_Local_Manually-Configured_PostgreSQL_Database_for_Use_with_the_Red_Hat_Enterprise_Virtualization_Manager