yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95817
[Bug 2109727] [NEW] removing an host from an aggregate should be accepted even if the host no longer exists
Public bug reported:
When we check whether some instances exist when removing an host from an
agreggate, we unfortunately have an exception if the host no longer
exists, which doesn't help operators to cleanup their environments.
We should check the cell mapping here instead of relying on the compute
record :
https://github.com/openstack/nova/blob/be4f4133a0ab391f55d26c0d91cd17d21870bf72/nova/compute/api.py#L6861
** Affects: nova
Importance: Undecided
Status: New
** Tags: api availability-zones
** Tags added: api availability-zones
--
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/2109727
Title:
removing an host from an aggregate should be accepted even if the host
no longer exists
Status in OpenStack Compute (nova):
New
Bug description:
When we check whether some instances exist when removing an host from
an agreggate, we unfortunately have an exception if the host no longer
exists, which doesn't help operators to cleanup their environments.
We should check the cell mapping here instead of relying on the
compute record :
https://github.com/openstack/nova/blob/be4f4133a0ab391f55d26c0d91cd17d21870bf72/nova/compute/api.py#L6861
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2109727/+subscriptions