yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

We recently hit an issue where an evacuating instance with dedicated
cpu_policy being pinned to same host CPUs as other instances with
dedicated cpu_policy. During subsequent resource audits we would see cpu
pinning errors.

The root cause appears to be the fact that the resource audit skips the
evacuating instance during migration phase of audit while instance was
rebuilding on new host.  It appears that _instance_in_resize_state()
returned "false" because the vm_state was vm_states.ERROR.  We allow
rebuilding from the ERROR state though, so we should consider it.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: compute

-- 
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/1688599

Title:
  resource audit races against evacuating instance

Status in OpenStack Compute (nova):
  New

Bug description:
  We recently hit an issue where an evacuating instance with dedicated
  cpu_policy being pinned to same host CPUs as other instances with
  dedicated cpu_policy. During subsequent resource audits we would see
  cpu pinning errors.

  The root cause appears to be the fact that the resource audit skips
  the evacuating instance during migration phase of audit while instance
  was rebuilding on new host.  It appears that
  _instance_in_resize_state() returned "false" because the vm_state was
  vm_states.ERROR.  We allow rebuilding from the ERROR state though, so
  we should consider it.

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