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

Bug 1129542

Summary: [SLA] [Text] ${detailsMessage} in case there are no available hosts with enough cores to run a VM
Product: [Retired] oVirt Reporter: Ilanit Stein <istein>
Component: ovirt-engine-coreAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: ecohen, gklein, iheim, jhunsaker, mavital, rbalakri, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: ovirt-3.5.0_rc3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:40:02 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:
Embargoed:
Attachments:
Description Flags
screen shot none

Description Ilanit Stein 2014-08-13 06:43:11 UTC
Description of problem:
When setting a VM with number of vcpu, higher than the cpu limit on the hosts,
the VM start operation fail (failure screen shot attached), and the error message includes ${detailsMessage} which should not appear to the user in such format. 

Version-Release number of selected component (if applicable):
ovirt-engine 3.5-rc1

How reproducible:
100%

Comment 1 Ilanit Stein 2014-08-13 13:32:14 UTC
Created attachment 926439 [details]
screen shot

Comment 2 Ilanit Stein 2014-10-02 08:39:15 UTC
Verified on vt-4.

Now message do not contain the '$':

Error while executing action:

rhel:

    Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
    The host <ip address> did not satisfy internal filter CPU because it does not have enough cores to run the VM.
    The host <ip address> did not satisfy internal filter CPU because it does not have enough cores to run the VM.

Comment 3 Tomer Saban 2014-10-13 13:51:38 UTC
*** Bug 1148974 has been marked as a duplicate of this bug. ***

Comment 4 Sandro Bonazzola 2014-10-17 12:40:02 UTC
oVirt 3.5 has been released and should include the fix for this issue.

Comment 5 Doron Fediuck 2015-05-01 09:32:11 UTC
*** Bug 1134714 has been marked as a duplicate of this bug. ***