Bug 1515165

Summary: Seeing cpu affinity is not supported messages on compute node
Product: Red Hat OpenStack Reporter: Sahid Ferdjaoui <sferdjao>
Component: openstack-novaAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: berrange, dasmith, ebeaudoi, eglynn, jmelvin, kchamart, knoel, mbooth, mburns, mlopes, mrezanin, nchandek, panbalag, rbalakri, saime, sbauza, sferdjao, sgordon, slinaber, srevivo, vromanso
Target Milestone: z7Keywords: Reopened, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-nova-14.0.9-2.el7ost Doc Type: Bug Fix
Doc Text:
Prior to this update, QEMU (also known as TCG) guests had an issue where the `guest.get_vcpu_info` method was throwing an exception indicating that 0 were vCPUs used on the host, regardless of how many guests were running. Consequently, this caused the 'get_available_resources' method to report incorrect vCPUs used values for the Compute node. This meant it was overcounting resource consumption for plain QEMU guests, as they can only ever consume 1 pCPU of time, regardless of vCPU count. With this update, if a host does not report detailed vCPU usage from libvirt, then it should default to reporting 1 vCPU per guest, so that the 'vcpus_used' field reports some reasonably meaningful data on host CPU usage. As a result, libvirt does not report that 'cpu affinity is not supported' when guests are running in TCG.
 Story Points: ---
Clone Of: 1420903 Environment:
Last Closed: 2018-04-03 10:31:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1420903, 1563067, 1591385    
Bug Blocks:    

Comment 8 errata-xmlrpc 2018-02-27 16:24:48 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.

https://access.redhat.com/errata/RHSA-2018:0369
Comment 9 Stephen Finucane 2018-04-03 09:06:09 UTC 
*** Bug 1563067 has been marked as a duplicate of this bug. ***