yahoo-eng-team team mailing list archive

[OpenStack Infra <1852759@xxxxxxxxxxxxxxxxxx>]

This issue was fixed in the openstack/nova queens-eol  release.

** Changed in: nova/queens
       Status: Fix Committed => 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/1852759

Title:
  false error log at compute restart during error out stuck instances

Status in OpenStack Compute (nova):
  Invalid
Status in OpenStack Compute (nova) pike series:
  Fix Released
Status in OpenStack Compute (nova) queens series:
  Fix Released
Status in OpenStack Compute (nova) rocky series:
  Fix Committed

Bug description:
  Since https://review.opendev.org/#/c/687565 is merged to stable/rocky
  a compute node without any allocations in placement will log an error
  at every nova-compute restart.

  Nov 15 15:02:41 ubuntu nova-compute[21876]: ERROR nova.compute.manager
  [None req-0ab61fb0-a780-4b84-ad07-3d6b3216b280 None None] Could not
  retrieve compute node resource provider
  5895faa5-01fd-46ee-8afb-6ddcf136f65e and therefore unable to error out
  any instances stuck in BUILDING state.

  The ERROR log is simply wrong. It happens because the placement report
  client does not differentiate between error received from placement
  and empty allocation dict received from placement. This only effects
  stable/rocky and older stable branches as in stein
  get_allocations_for_resource_provider() was enhanced to raise instead
  of returning {} if placement returned an error [1].

  [1]
  https://github.com/openstack/nova/commit/f534495a427d1683bc536cf003ec02edbf6d8a45

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