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

Bug 1360363

Summary: engine-setup instructs to setup a remote dwh even if one already is
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Setup.EngineAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.0CC: bugs, dfediuck, lsvaty, sbonazzo, ylavi
Target Milestone: ovirt-4.0.5Flags: rule-engine: ovirt-4.0.z+
ylavi: planning_ack+
sbonazzo: devel_ack+
lsvaty: testing_ack+
Target Release: 4.0.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1379147 (view as bug list) Environment:
Last Closed: 2017-01-18 07:39:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2016-07-26 13:53:36 UTC
Description of problem:

If choosing 'No' when asked about DWH, engine-setup says:

          The engine requires access to the Data Warehouse database.
          Data Warehouse was not set up. Please set it up on some other machine and configure access to it on the engine.

It does this also if dwh is set up remotely.

It should not.

It can check this either by checking dwhHostname in engine db table dwh_history_timekeeping or, since 4.0, by checking if we have access to dwh db.

Comment 1 Lukas Svaty 2016-10-18 14:19:02 UTC
verified in ovirt-engine-setup-4.0.5.1-0.1.el7ev.noarch