Bug 1549153

Summary: Events coming to soon on refresh caps
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.InfraAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Pavol Brilla <pbrilla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: alkaplan, bugs, danken, lsvaty, lveyde, mperina, myakove, rnori
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:01:35 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:

Description Michael Burman 2018-02-26 14:27:08 UTC 
Description of problem:
Events coming to soon on refresh caps.

Only now we are aware of a change that was done in the refresh caps behaviour and it's not a good change. 
Now the events coming too soon, they come before the operation was actually succeeded.
In our automation runs we are depend on this events to be true and come only when the operation was actually done on the host. If it comes before that, it's bad. 

Version-Release number of selected component (if applicable):
4.2.2.1-0.1.el7

How reproducible:
100

Steps to Reproduce:
1. Run refresh caps in the UI

Actual results:
Event return immediately before the operation was done on the host

Expected results:
Event must return only when done on the host
Comment 1 Martin Perina 2018-02-26 15:36:16 UTC 
Ravi, is this related to non-blocking threads changes?
Comment 2 Martin Perina 2018-03-06 08:11:34 UTC 
Not included in ovirt-engine-4.2.2.2 build, moving back to MODIFIED
Comment 3 Pavol Brilla 2018-03-21 14:31:26 UTC 
Verified on 4.2.2.4-0.1.el7
Comment 4 Pavol Brilla 2018-03-21 14:31:26 UTC 
Verified on 4.2.2.4-0.1.el7
Comment 5 Sandro Bonazzola 2018-03-29 11:01:35 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.