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

Bug 1491115

Summary: Cast failure @ EventQueueMonitor: java.lang.Integer cannot be cast to java.lang.Long
Product: [oVirt] ovirt-engine Reporter: Yaniv Kaul <ykaul>
Component: BLL.InfraAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, lsvaty, mperina, oourfali, rnori
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:47:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

Description Yaniv Kaul 2017-09-13 06:29:58 UTC
Created attachment 1325207 [details]
engine log

Description of problem:
Not sure what the cause is and how it affects the flow, but in an ovirt-system-tests engine log saw the following:

2017-09-13 00:44:55,565-04 ERROR [org.ovirt.engine.core.bll.eventqueue.EventQueueMonitor] (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Failed at submitEventSync, for pool '5f0b4f9c-d88d-43a8-9ddf-dc3ad
fae5ff5': java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long
2017-09-13 00:44:55,565-04 ERROR [org.ovirt.engine.core.bll.eventqueue.EventQueueMonitor] (org.ovirt.thread.EE-ManagedThreadFactory-engine-Thread-25) [77fefd] Exception during process of events for pool '5f0b4f9
c-d88d-43a8-9ddf-dc3adfae5ff5': java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long


Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170912134930.gitc81ca84.el7.centos

How reproducible:
Did not try yet.

Comment 2 Lukas Svaty 2017-09-14 12:06:30 UTC
Can you please check if ovirt system tests if the issue disappeared? Not sure where it was found.

Comment 3 Sandro Bonazzola 2017-12-20 10:47:07 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.