Change I7b8622b178d5043ed1556d7bdceaf60f47e5ac80 started deleting
the associated resource provider when a compute service is deleted.
However, the delete_resource_provider cascade=True logic only looks
for instances on the given compute service host being deleted which
will miss (1) allocations remaining from evacuated servers and
(2) unconfirmed migrations.
Attempting to delete the resource provider results in an
ResourceProviderInUse error which delete_resource_provider ignores
for legacy reasons. This results in the compute service being
deleted but the resource provider being orphaned. What's more,
attempting to restart the now-deleted compute service will fail
because nova-compute will try to create a new resource provider
with a new uuid but with the same name (based on the hypervisor
hostname). That failure is actually reported in bug 1817833.
NOTE(mriedem): Note that in this backport a simple version of
assertFlavorMatchesUsage is added since the original version from
change If6aa37d9b6b48791e070799ab026c816fda4441c is not in Rocky.
Change-Id: I69f52f1282c8361c9cdf90a523f3612139cb8423
Related-Bug: #1829479
Related-Bug: #1817833
(cherry picked from commit 2629d65fbc15d8698f98117e0d6072810f70da03)
(cherry picked from commit b18e42d20bd7d341e713292bdb179ae8e5530d33)
Reviewed: https:/ /review. opendev. org/698106 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=6eda7409fff 75449c97843b2d6 ead0b3267a1099
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 6eda7409fff7544 9c97843b2d6ead0 b3267a1099
Author: Matt Riedemann <email address hidden>
Date: Thu Jun 6 13:41:09 2019 -0400
Add functional recreate test for bug 1829479 and bug 1817833
Change I7b8622b178d504 3ed1556d7bdceaf 60f47e5ac80 started deleting resource_ provider cascade=True logic only looks
the associated resource provider when a compute service is deleted.
However, the delete_
for instances on the given compute service host being deleted which
will miss (1) allocations remaining from evacuated servers and
(2) unconfirmed migrations.
Attempting to delete the resource provider results in an viderInUse error which delete_ resource_ provider ignores
ResourcePro
for legacy reasons. This results in the compute service being
deleted but the resource provider being orphaned. What's more,
attempting to restart the now-deleted compute service will fail
because nova-compute will try to create a new resource provider
with a new uuid but with the same name (based on the hypervisor
hostname). That failure is actually reported in bug 1817833.
NOTE(mriedem): Note that in this backport a simple version of rMatchesUsage is added since the original version from 91e070799ab026c 816fda4441c is not in Rocky.
assertFlavo
change If6aa37d9b6b487
Change-Id: I69f52f1282c836 1c9cdf90a523f36 12139cb8423 98f98117e0d6072 810f70da03) 1e713292bdb179a e8e5530d33)
Related-Bug: #1829479
Related-Bug: #1817833
(cherry picked from commit 2629d65fbc15d86
(cherry picked from commit b18e42d20bd7d34