Bug 987822

Summary: start VM will show unintialized action and type CDA message
Product: Red Hat Enterprise Virtualization Manager Reporter: Maor <mlipchuk>
Component: ovirt-engine-userportalAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED CURRENTRELEASE QA Contact: sefi litmanovich <slitmano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, iheim, michal.skrivanek, mlipchuk, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: is7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 22:12:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1019461    
Attachments:
Description Flags
the can do action none

Description Maor 2013-07-24 08:45:33 UTC
Created attachment 777660 [details]
the can do action

Description of problem:
Pressing on the run button while the VM is already being started will show an uninitialized CDA message

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Press on the run button
2. Press on the run button immediately afater
3.

Actual results:
getting the message:
Cannot ${action} ${type}. Related operation is currently in progress. Please try again later.

Expected results:
Cannot Run VM. Related operation is currently in progress. Please try again later.

Additional info:

Comment 1 Maor 2013-07-24 16:18:19 UTC
has been produced on nott04 user portal (on ovirt it does no reproduced)

Comment 2 Michal Skrivanek 2013-07-25 14:18:24 UTC
is this a regression?

Comment 3 Maor 2013-07-25 14:25:52 UTC
it should be a regression since it worked before.
Keep in mind that when I verified that on ovirt it didn't reproduced, so it could be, that the fix was already merged to RHEVM, just need to make sure that it was already in.

Comment 4 Michal Skrivanek 2013-07-25 14:28:15 UTC
good, then let QA just test it then

Comment 5 sefi litmanovich 2013-09-03 12:37:09 UTC
verified on rhevm-3.3, is12.
double clicking on the run button returns the following message:
*Cannot run VM.The VM status is illegal

Comment 6 Itamar Heim 2014-01-21 22:12:17 UTC
Closing - RHEV 3.3 Released