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

Bug 1363958

Summary: Clean reports related configuration when upgrading to 4.0
Product: [oVirt] ovirt-engine Reporter: Sandro Bonazzola <sbonazzo>
Component: Setup.EngineCommonAssignee: Yedidyah Bar David <didi>
Status: CLOSED WONTFIX QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0.2.4CC: bugs, mperina, ylavi
Target Milestone: ---Flags: sbonazzo: ovirt-4.1-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-06 10:36:49 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 Sandro Bonazzola 2016-08-04 07:08:11 UTC 
Description of problem:
In 3.6 it was possible to install ovirt-engine and ovirt-engine-reports.
In 4.0 ovirt-engine-reports doesn't exist anymore.
When migrating from el6 -> el7 or fc22 -> fc23 using backup / restore, the reports bits won't be restored after fixing bug #1340810.
The only case left is in place upgrade on el7 which should be handled ensuring that the reports config left on the system doesn't break the engine.
Comment 1 Yedidyah Bar David 2016-09-01 08:26:55 UTC 
We also need to decide if we support, or at least not prevent, running reports 3.6 on a separate machine. If so, we need to keep [1].

I'd say we probably want two questions:

1. oVirt Reports was found set up on this machine. Reports is not available in oVirt 4.0. Remove it?

2. The engine is configured to access oVirt Reports on {url}. Reports is not available in oVirt 4.0. Remove this configuration?

For (2.), we can add logic to check if it's on same or different machine (will be ugly, because we do not have REPORTS_FQDN, so will have to parse ENGINE_REPORTS_BASE_URL), and/or try to GET it and see if this succeeded. Or do nothing and let the user decide.

[1] /etc/ovirt-engine/engine.conf.d/10-setup-reports-access.conf
Comment 2 Yedidyah Bar David 2016-09-18 08:05:58 UTC 
In a private discussion Yaniv decided to remove this file as well.

This means that running 3.6 reports against a 4.0 engine is not forbidden, but any connection between them, including sso, is.