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

Bug 1149483

Summary: A VM is allowed to run even before it’s ready after creation
Product: Red Hat Enterprise Virtualization Manager Reporter: Gilad Lazarovich <glazarov>
Component: ovirt-engine-webadmin-portalAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, ecohen, iheim, lsurette, michal.skrivanek, ofrenkel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Reopened
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-02 10:28:43 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:
Attachments:
Description Flags
VM allowed to Run before it's fully ready none

Description Gilad Lazarovich 2014-10-05 12:03:18 UTC
Created attachment 944030 [details]
VM allowed to Run before it's fully ready

Description of problem:
A VM is allowed to run even before it’s ready after creation

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

How reproducible:
100%

Steps to Reproduce:
1. Create a new VM with at least one disk
2. Immediately attempt to Run this VM

Actual results:
An error message is presented noting that VM cannot be run with the appropriate error message

Expected results:
The VM should only be allowed to run once it’s ready, this includes the Run button

Additional info:
In general, we should block any operations while another task is running unless it doesn’t interfere with it

Comment 1 Michal Skrivanek 2014-10-06 08:05:41 UTC
This was a design decision and is an intended behavior. The VM itself is complete, it's the disk creation which goes on in the background

Comment 2 Aharon Canan 2014-10-06 08:24:22 UTC
Although the VM completed we still can't run it (we get error message)

in such case it is much more user friendly to greyed out the power on button.

if it is the design we probably should change it.

Comment 3 Omer Frenkel 2014-10-06 09:09:01 UTC
this is how it suppose to work.
the main tab buttons are enabled/disabled according to the vm status.
since the vm is down, its enabled even if one of the disks/snapshots/.. is blocking some operation. 

it does not make sense for the UI to get all this info from the backend all the time just for getting the buttons enabled/disabled, and there is always a chance that this info is out of date because of polling times.

the user still get an informative message.

i still suggest to close as wont-fix/not-a-bug