yahoo-eng-team team mailing list archive

[Shi Yan <yanshi.403@xxxxxxxxx>]

Public bug reported:

Description
===========
We are using the nova stein version.
When adding/removing host from aggregate, nova should sync the host aggregate to placement resource provider aggregate as well. But from our test, it is not working.

Steps to reproduce
==================
1. Check a specific compute node resource provider aggregate
2. Create a new host aggregate and add the compute node into the aggregate
3. Check the compute node resource provider aggregate again to see if the additional aggreate is added

(We got the similar error when removing host from an existing aggregate)

Expected result
===============
An additional resource provider aggregate for the compute node

Actual result
=============
No change.

Logs & Configs
==============

from nova-api:

May 07 09:54:06 nova-api nova-api[26742]: 2020-05-07 09:54:06.364 26742
WARNING nova.compute.api [req-b4542212-7a5c-4d81-b602-4702634015b8
c0645ff94b864d3d84c438d9855f9cea 9427903ca1544f0795ba4117d55ed9b2 -
default default] Failed to associate cc2 with a placement aggregate: No
such resource provider cc2.. This may be corrected after running nova-
manage placement sync_aggregates.:
nova.exception.ResourceProviderNotFound: No such resource provider cc2.

Note:
cc2 is the hostname but the name of the resource provider is fqdn(with domain). I think that is reason why the resource provider cannot be found.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Nova host aggregate cannot sync to placement

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  We are using the nova stein version.
  When adding/removing host from aggregate, nova should sync the host aggregate to placement resource provider aggregate as well. But from our test, it is not working.

  Steps to reproduce
  ==================
  1. Check a specific compute node resource provider aggregate
  2. Create a new host aggregate and add the compute node into the aggregate
  3. Check the compute node resource provider aggregate again to see if the additional aggreate is added

  (We got the similar error when removing host from an existing
  aggregate)

  Expected result
  ===============
  An additional resource provider aggregate for the compute node

  Actual result
  =============
  No change.

  Logs & Configs
  ==============

  from nova-api:

  May 07 09:54:06 nova-api nova-api[26742]: 2020-05-07 09:54:06.364
  26742 WARNING nova.compute.api [req-b4542212-7a5c-
  4d81-b602-4702634015b8 c0645ff94b864d3d84c438d9855f9cea
  9427903ca1544f0795ba4117d55ed9b2 - default default] Failed to
  associate cc2 with a placement aggregate: No such resource provider
  cc2.. This may be corrected after running nova-manage placement
  sync_aggregates.: nova.exception.ResourceProviderNotFound: No such
  resource provider cc2.

  Note:
  cc2 is the hostname but the name of the resource provider is fqdn(with domain). I think that is reason why the resource provider cannot be found.

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