Bug 1037645

Summary: misleading message when trying to run VM on cluster with no hosts
Product: [Retired] oVirt Reporter: Jiri Moskovcak <jmoskovc>
Component: ovirt-engine-coreAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: dfediuck, gchaplik, iheim, michal.skrivanek, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:26:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Moskovcak 2013-12-03 14:31:15 UTC 
Description of problem:
I created a new VM in a cluster which did contain any hosts. Whe I tried to start the VM i got this:

<snip>
Error while executing action: 

windows:
Cannot run VM. There is no host that satisfies current scheduling constraints. See bellow for details:

<snip>

Version-Release number of selected component (if applicable):
current git (644bb78868f6ba808711d282e08bee939b60d568)

How reproducible:
100%

Steps to Reproduce:
1. create a VM in a cluster with no host
2. try to run the VM
3.

Actual results:
Error message about scheduling constraints.

Expected results:
Error message saying that there is no host in the cluster
Comment 1 Itamar Heim 2014-01-12 08:43:20 UTC 
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
Comment 2 Michal Skrivanek 2014-02-14 14:47:59 UTC 
@sla - can we maybe get a better reason from the scheduler?
Comment 3 Sandro Bonazzola 2014-03-04 09:23:12 UTC 
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 4 Sandro Bonazzola 2014-05-08 13:56:36 UTC 
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
Comment 5 Sandro Bonazzola 2014-10-17 12:26:05 UTC 
oVirt 3.5 has been released and should include the fix for this issue.