Reviewed: https://review.openstack.org/581086 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f0f680b492c82f4f5c4163b0534dacc315b6dce5 Submitter: Zuul Branch: master
commit f0f680b492c82f4f5c4163b0534dacc315b6dce5 Author: Jay Pipes <[email protected]> Date: Mon Jul 9 12:41:05 2018 -0400 delete consumers which no longer have allocations We made the decision [1] to delete consumer records when those consumers no longer had any allocations referring to them (as opposed to keeping those consumer records around and incrementing the consumer generation for them). This patch adds a small check within the larger AllocationList.create_all() and AllocationList.delete_all() DB transactions that deletes consumer records when no allocation records remain that reference that consumer. This patch does not, however, attempt to clean up any "orphaned" consumer records that may have been created in previous calls to PUT|POST /allocations that removed the last remaining allocations for a consumer. [1] https://goo.gl/DpAGbW Change-Id: Ic2b82146d28be64b363b0b8e2e8d180b515bc0a0 Closes-bug: #1780799 ** Changed in: nova Status: In Progress => Fix Released -- 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/1780799 Title: Consumers with no allocations should be auto-deleted Status in OpenStack Compute (nova): Fix Released Bug description: When an allocation is POST'd or PUT'd and the set of allocations for a consumer is deleted (indicated with an empty dict for the allocations), then the consumer should be automatically deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1780799/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
