Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1195114 - Engine does not filter duplicate action on the same entity
Engine does not filter duplicate action on the same entity
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.5.0
Unspecified Unspecified
unspecified Severity high
: ---
: 3.5.1
Assigned To: Moti Asayag
Moti Asayag
infra
: CodeChange, ZStream
Depends On: 1172699
Blocks: 1193058 1197441
  Show dependency treegraph
 
Reported: 2015-02-23 01:37 EST by rhev-integ
Modified: 2016-02-10 14:20 EST (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1172699
Environment:
Last Closed: 2015-04-28 14:48:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 36102 master NEW engine: Prevents duplicates parameters in multiple actions Never
Red Hat Product Errata RHSA-2015:0888 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.5.1 update 2015-04-28 18:40:04 EDT

  None (edit)
Comment 2 Pavel Novotny 2015-03-16 05:21:59 EDT
Cannot reproduce with rhevm-3.5.0-0.31.el6ev (vt13.10).

In webadmin, I selected a VM and double clicked the run icon, but I got the relevant message "Cannot run VM. Related operation is currently in progress. Please try again later.".

@Arik, can you please share more details how to reproduce this?
Thanks.
Comment 3 Arik 2015-03-16 14:31:59 EDT
(In reply to Pavel Novotny from comment #2)
> Cannot reproduce with rhevm-3.5.0-0.31.el6ev (vt13.10).
> 
> In webadmin, I selected a VM and double clicked the run icon, but I got the
> relevant message "Cannot run VM. Related operation is currently in progress.
> Please try again later.".

The multiple requests must be sent together to the engine. In this scenario they are sent in two steps so the second is blocked by the locking mechanism which is fine.

> 
> @Arik, can you please share more details how to reproduce this?
> Thanks.

I patched the ui to send the same request twice, I didn't manage to reproduce it differently as well.
Comment 4 Pavel Novotny 2015-03-17 12:07:44 EDT
(In reply to Arik from comment #3)
> (In reply to Pavel Novotny from comment #2)
[snip]
> > 
> > @Arik, can you please share more details how to reproduce this?
> > Thanks.
> 
> I patched the ui to send the same request twice, I didn't manage to
> reproduce it differently as well.

Ok, I see. Unfortunately we are not able to patch UI for verification. I am moving QA Contact back to assignee (same as it is in original bug 1172699).
Comment 5 Oved Ourfali 2015-03-25 03:57:19 EDT
It is a code change.
Moving to VERIFIED.
Comment 6 errata-xmlrpc 2015-04-28 14:48:04 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHSA-2015-0888.html

Note You need to log in before you can comment on or make changes to this bug.