yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

When deleting a resource provider the spec says that the resource
provider's inventory and associated aggregates should be deleted:

    http://specs.openstack.org/openstack/nova-
specs/specs/newton/implemented/generic-resource-pools.html#delete-
resource-providers-uuid

In version 1.1 of the placement API, inventory is being deleted, but
aggregate associations are left untouched. This means that in the
following case the resulting aggregates will be wrong:

* create an rp with a known uuid (this is allowed and expected)
* associate some aggregates (a, b, c)
* delete the rp
* recreate the rp with same uuid
* query the associated aggregates get 'a, b, c' but expect []

Note that the set_aggregates functionality (and the associated PUT API)
is a full replace so any time the associated aggregates are updated, the
input in that request becomes the whole set of associated aggregates.
This bug is only present in the case where aggregates were present on
the previous incarnation of a resource provider but should not be on the
current incarnation.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement

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

Title:
  When deleting a resource provider in the placement api the rp's
  associated aggregates are not cleaned up

Status in OpenStack Compute (nova):
  New

Bug description:
  When deleting a resource provider the spec says that the resource
  provider's inventory and associated aggregates should be deleted:

      http://specs.openstack.org/openstack/nova-
  specs/specs/newton/implemented/generic-resource-pools.html#delete-
  resource-providers-uuid

  In version 1.1 of the placement API, inventory is being deleted, but
  aggregate associations are left untouched. This means that in the
  following case the resulting aggregates will be wrong:

  * create an rp with a known uuid (this is allowed and expected)
  * associate some aggregates (a, b, c)
  * delete the rp
  * recreate the rp with same uuid
  * query the associated aggregates get 'a, b, c' but expect []

  Note that the set_aggregates functionality (and the associated PUT
  API) is a full replace so any time the associated aggregates are
  updated, the input in that request becomes the whole set of associated
  aggregates. This bug is only present in the case where aggregates were
  present on the previous incarnation of a resource provider but should
  not be on the current incarnation.

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