DWH needs to align with oVirt engine and use OpenJDK 11 instead of 8
Note for QE, Please run full verification of DWH for this bug.
Verified on: ovirt-engine-dwh-setup-4.4.0-0.0.master.20190901182033.el7ev.noarch ovirt-engine-setup-4.4.0-0.14.master.el7.noarch Steps: 1. Assure java environment version # java -v 2. Build: 2.1. On a separated machine (from the 4.4 engine one) install ovirt-engine-dwh-setup package 2.2. Run # engine-setup and set to "Configure Data Warehouse on this host" 2.3. Answer questions pointing to a 4.4 engine and finish installation 2.4. # systemctl status ovirt-engine-dwhd 2.5. Assure running java version on dwhd: # python -c "from ovirt_engine import java; print(java.Java().getJavaHome())" 2.6. Open the engine web server and check for if dashboard is working as expected (manually refreshing it as well) 3. Runtime: 3.1. Enable debug logging on the machine with the dwh: # echo "DWH_AGGREGATION_DEBUG=true" >> /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/logging.conf 3.2. Restart service: # systemctl restart ovirt-engine-dwhd 3.3. Check for timely statistical sync logs: # grep SampleTimeKeepingJob /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log # grep HourlyTimeKeepingJob /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log 3.5. Open the engine web server and check for if dashboard is working as expected (manually refreshing it as well) Results: 2.4. Service is running as expected 2.5. Path for openjdk 11 shown 2.5. Dashboard showing data and updating as expected 3.3 Timely statistical logs being logged as expected 3.5. Dashboard showing data and updating as expected
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.