Bug 1569853 - misleading info about db if misses uuid-ossp extension
Summary: misleading info about db if misses uuid-ossp extension
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 4.2.3.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.3.0
: ---
Assignee: Ido Rosenzwig
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-20 06:38 UTC by Jiri Belka
Modified: 2018-07-02 07:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-02 07:39:11 UTC
oVirt Team: Integration
rule-engine: ovirt-4.3+


Attachments (Terms of Use)

Description Jiri Belka 2018-04-20 06:38:57 UTC
Description of problem:

engine-setup
...
[ INFO  ] Stage: Setup validation
         
          PostgreSQL uuid-ossp extension is not installed in  the engine :database
 ^^^^^^^^ here, invalid db name
          Please run the following commands from psql prompt  with database administrator privileges and run  engine-setup again:
          DROP FUNCTION IF EXISTS uuid_generate_v1();
          CREATE EXTENSION "uuid-ossp";
          For DROP you should connect to the engine database,
            even though you use admin user.
[ ERROR ] Failed to execute stage 'Setup validation': uuid-ossp extension is not installed on database
[ INFO  ] Stage: Clean up
...

my dbs were: remotedb, remoteodb

Version-Release number of selected component (if applicable):
4.2.3

How reproducible:
100%

Steps to Reproduce:
1. have 9.5 without uuid-ossp extension (i used remote db setup)
2. engine-setup from 4.1 to 4.2 (upgrade)
3.

Actual results:
misleading db name in the output

Expected results:
db name should be valid or db name should not be there at all

Additional info:

Comment 1 Yaniv Lavi 2018-07-02 07:39:11 UTC
Closing old bugs.
Please reopen if still relevant.
In any case patches are welcomed.


Note You need to log in before you can comment on or make changes to this bug.