Bug 1018201

Summary: CPU pinning option is not available for the VMs running on "Local on Host" type DataCenter.
Product: Red Hat Enterprise Virtualization Manager Reporter: Udayendu Sekhar Kar <ukar>
Component: ovirt-engineAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: high    
Version: 3.2.0CC: acathrow, dfediuck, iheim, lpeer, mavital, Rhev-m-bugs, rpai, s.kieske, yeylon
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: is26 Doc Type: Enhancement
Doc Text:
The CPU pinning option is now available for virtual machines running on the Local on Host type data center, and is enabled by default even if the virtual machine is not pinned to the host.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 17:38:01 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:
Bug Depends On:    
Bug Blocks: 1044030    
Attachments:
Description Flags
no_host_sub_tab none

Comment 1 Artyom 2013-11-14 14:00:47 UTC 
Created attachment 823962 [details]
no_host_sub_tab

Checked on is23, still no host sub-tab under vm edit menu.
See screenshot for details.
Comment 2 Gilad Chaplik 2013-11-14 15:11:20 UTC 
(In reply to Artyom from comment #1)
> Created attachment 823962 [details]
> no_host_sub_tab
> 
> Checked on is23, still no host sub-tab under vm edit menu.
> See screenshot for details.

cpu-pinning is under resource allocation tab, and in case it's local dc, the cpu-pinning is enalbed even if the vm isn't pinned to host.

Moving back to ON_QA
Comment 3 Gilad Chaplik 2013-11-14 15:40:50 UTC 
there ia an engine validation problem (in local dc), also the error message is unlocalized.
moving back to assign
Comment 4 Artyom 2013-12-06 10:00:02 UTC 
Verified on is26, cpu pinning option work fine.
Comment 5 errata-xmlrpc 2014-01-21 17:38:01 UTC 
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-0038.html