Nova's v2 server group API list() call returns a list of members which
includes deleted instances. Is this valid behavior? Should requestors make
the determination that these are deleted instances and act accordingly, or
is this something that changed in Nova and that Nova will fix?
The whole story:
Trove's gate has begun to fail with a very repeatable and specific pattern
where a test finds that there are left-over members in a server group and
therefore does not delete the server group. See .
The tests in question create a server group (anti-affinity) and add multiple
instance to it. The instances are then deleted, and the tests wait to ensure
that the instances are in fact deleted. The tests then attempt to delete the
server group. The code (in trove) that determines whether or not to delete
the server group has contained (since its creation) a check to ensure that
the group is only deleted if it is empty (has no members) or has a single
instance (the last instance being deleted).
Now however, since the server groups membership shows deleted instances,
trove's code isn't deleting the server group and our tests are failing.
This is illustrated from the CLI based example (attached).
OpenStack Development Mailing List (not for usage questions)