yahoo-eng-team team mailing list archive

[Corey Bryant <1877229@xxxxxxxxxxxxxxxxxx>]

This is not yet fixed in upstream or Ubuntu for releases prior to
Victoria.

** Also affects: nova (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Impish)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Kinetic)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: nova (Ubuntu Impish)
       Status: New => Fix Released

** Changed in: nova (Ubuntu Kinetic)
       Status: New => Fix Released

** Changed in: nova (Ubuntu Jammy)
       Status: New => Fix Released

** Changed in: nova (Ubuntu Focal)
       Status: New => Triaged

** Changed in: nova (Ubuntu Focal)
   Importance: Undecided => High

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/wallaby
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/zed
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/ussuri
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/victoria
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/yoga
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/xena
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/zed
       Status: New => Fix Released

** Changed in: cloud-archive/yoga
       Status: New => Fix Released

** Changed in: cloud-archive/xena
       Status: New => Fix Released

** Changed in: cloud-archive/wallaby
       Status: New => Fix Released

** Changed in: cloud-archive/victoria
       Status: New => Fix Released

** Changed in: cloud-archive/ussuri
   Importance: Undecided => High

** Changed in: cloud-archive/ussuri
       Status: New => Triaged

-- 
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 Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Fix Released
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in Ubuntu Cloud Archive yoga series:
  Fix Released
Status in Ubuntu Cloud Archive zed series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Focal:
  Triaged
Status in nova source package in Impish:
  Fix Released
Status in nova source package in Jammy:
  Fix Released
Status in nova source package in Kinetic:
  Fix Released

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 for the compute node, but we use fqdn for the hypervisor. So the name of the resource provider is fqdn(with domain). I think that is the reason why the resource provider cannot be found.

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