Created attachment 1591088 [details] Closed Connection log Description of problem: Get exception while a connection closed Version-Release number of selected component (if applicable): redhat-release-server-7.7-10.el7.x86_64 rhv-release-4.3.5-6-001.noarch How reproducible: Steps to Reproduce: 1. Config "DEBUG" to 'ovirt-engine-dwhd.log' 2. Monitor the env 24-48 - include 'Deletion' cycle 3. Check the log if have an exception on a closed connection Actual results: have an exception on a closed connection Expected results: No exception on a closed connection Additional info: Attached example of an exception on a closed connection
This issue seems to appear also when upgrading 4.3.5 -> 4.4. Engine upgrade (using engine setup) fails on this. Test failure: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15079/testReport/(root)/001_upgrade_engine/running_tests___upgrade_from_release_suite_el7_x86_64___test_initialize_engine/ Relevant ovirt-engine-dwhd log: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15079/artifact/upgrade-from-release-suite.el7.x86_64/test_logs/upgrade-from-release-suite-master/post-001_upgrade_engine.py/lago-upgrade-from-release-suite-master-engine/_var_log/ovirt-engine-dwh/ovirt-engine-dwhd.log
We should verify all flows: DWH Sampling , hourly, daily aggregations and deletion as well as upgrade flow.
No errors in log. Sampling, daily/hourly aggregation, deletion works as expected. Upgrade issues not seen anymore. verified in ovirt-engine-dwh-4.3.5.1-1.el7ev.noarch ovirt-engine-4.3.5.5-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.5 async release, published on August 5th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.5 async 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.
*** Bug 1752852 has been marked as a duplicate of this bug. ***