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

Bug 1148974

Summary: The host <host> did not satisfy internal filter CPU because ${detailMessage}.
Product: Red Hat Enterprise Virtualization Manager Reporter: Jake Hunsaker <jhunsaker>
Component: ovirt-engine-webadmin-portalAssignee: Tomer Saban <tsaban>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: dfediuck, ecohen, gklein, iheim, lsurette, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-13 13:51:38 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:

Description Jake Hunsaker 2014-10-02 19:22:59 UTC
Description of problem:

When trying to start a VM that has more vCPUs than any hypervisor has available, there is an unexpanded "${detailMessage}" variable in the error dialog window.

Version-Release number of selected component (if applicable):
rhevm-3.5.0 beta 1

How reproducible:
Always

Steps to Reproduce:
1. Create a VM with more vCPUs than any hypervisors can provide
2. Try to start the VM
3.

Actual results:
Unexpanded variable is included in the dialog


Expected results:
Error dialog should be expanded

Additional info:

Full error dialog is:

Cannot run VM. There is no host that satisfies the current scheduling constraints. See below for details:  
- Cannot run VM. There are no available running Hosts with enough cores in the VM's Cluster .    

- The host <host> did not satisfy internal filter CPU because ${detailMessage}.


This seems similar to BZ 1142130 so perhaps a common mechanism?

Comment 1 Tomer Saban 2014-10-13 13:51:38 UTC

*** This bug has been marked as a duplicate of bug 1129542 ***