Bug 1068717
| Summary: | [RHEV] ability on RHEV to notify the lack of required CPUs to start a VM | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Javier Coscia <jcoscia> |
| Component: | ovirt-engine | Assignee: | Gilad Chaplik <gchaplik> |
| Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.0 | CC: | aberezin, acathrow, cpelland, dfediuck, gchaplik, iheim, lbopf, lpeer, mavital, mrezanin, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.4.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | sla | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, when insufficient CPUs existed to start a virtual machine, the VM was simply paused, and the Red Hat Enterprise Virtualization web portal produced no error message. Now, the following error is produced in the web portal and in the engine log: "Cannot run VM. There are no available running Hosts with enough cores in VM's Cluster. Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details: The host did not satisfy internal filter CPU."
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-09 15:04:37 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
Javier Coscia
2014-02-21 18:05:49 UTC
This should have been resolved by the new RHEV scheduler starting RHEV 3.3. Gilad, can please verify it? component seems wrong? (In reply to Itamar Heim from comment #6) > component seems wrong? let's leave it on sla, till I test Doron's request. (In reply to Gilad Chaplik from comment #7) > (In reply to Itamar Heim from comment #6) > > component seems wrong? > > let's leave it on sla, till I test Doron's request. I misunderstood. I will check it out while checking it. Starting rhev 3.3 the new scheduler provides the relevant information for each host if it cannot start a VM. So failure on network or memory or cpu info is propagated to the user, and also appears in the log file. Moving to be tested in 3.4. Verified on rhevm 6 with rhevh RHEV Hypervisor - 6.5 - 20140408.0.el6ev
Vm have 8 cpus(8 sockets), host have 4 socets, when try to run vm, appear error message:
Error while executing action:
vm1:
Cannot run VM. There are no available running Hosts with enough cores in VM's Cluster .
Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:
The host rose01.qa.lab.tlv.redhat.com did not satisfy internal filter CPU.
the same thing appear in engine.log
Changing component to rhev-hypervisor as we are going to move qemu-kvm-rhev component to RHEL7 product to be able to follow RHEL release cycle for qemu-kvm-rhev-2.0.0 and newer. Please check correct component assignment. Miroslav, why is this specific for rhev-h and not any hypervisor? ie- as you can see from the verification in comment 10, the issue is handled in the engine regardless of the hypervisor type. So if any this should have been an engine issue. Component set accordingly. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html |