yahoo-eng-team team mailing list archive

[Elod Illes <1848308@xxxxxxxxxxxxxxxxxx>]

** Also affects: nova/train
   Importance: Undecided
       Status: New

** Changed in: nova/train
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1848308

Title:
  Impossible to set instance CPU policy to 'shared' through flavor image
  property

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) train series:
  Fix Released

Bug description:
  According to the content defined in doc
  https://docs.openstack.org/nova/latest/admin/cpu-topologies.html
  #customizing-instance-cpu-pinning-policies, the instance CPU
  allocation policy could be explicitly set through instance flavor
  property 'hw:cpu_policy', or its corresponding image property
  'hw_cpu_policy'.

  One general rule to solve the conflict between these two properties, if I understand it correctly, is if 'hw:cpu_policy' is not given with any policy, then it should take the policy from 'hw_cpu_policy'. But currently, if 'hw_cpu_policy' is set as 'shared' and no value set in 'hw:cpu_policy' the logic in 'hardware.get_cpu_policy_constraint' tells that there is no CPU policy (throug return a value of None).
  In this case, it should return the "shared" policy.

  This issue is first reported in https://review.opendev.org/#/c/688603/
  but without tracking with a bug ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1848308/+subscriptions