after a tenant has deleted a resource, subsequent calls on new resources are dropped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Astara |
High
|
Adam Gandelman |
Bug Description
The tenant resource cache, which we use to cache the id of tenant resources so as to avoid neutron calls, never removes its entries when a resource is deleted. This causes an issue where a tenant cannot re-create a deleted resource, ie:
* Create a network, subnet, router, etc.
* Delete router interface, delete subnet, delete router, delete network
* Create a network, subnet, router
* The orchestrator gets the create event, attempts to resolve the router id via the cache, gets the previous router and ignores message because it is a message for a deleted resource.
We need to add some callbacks to invalidate entries from the resource cache when we do the rest of deletion.
Changed in astara: | |
importance: | Undecided → High |
Changed in astara: | |
status: | New → In Progress |
Changed in astara: | |
milestone: | none → mitaka-2 |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5fed2a704162d42
Author: Adam Gandelman <email address hidden>
Date: Wed Jan 6 12:24:50 2016 -0800
Cleanup deleted resource from the tenant resource cache
When a resource is deleted, its not currently removed from the tenant
resource cache. This causes a cache hit if the tenant attempts to re-create
the same type of resource, but the resource is then later ignored because
it has been deleted. This adds a callback used by the TRM to remove it
from the resource cache when its state machine is deleted.
Change-Id: I5dcbeda7de240a
Closes-bug: #1531597
Changed in astara: | |
status: | In Progress → Fix Released |
Changed in astara: | |
assignee: | nobody → Adam Gandelman (gandelman-a) |
summary: |
after a tenant has deleted a resource, subsequent calls on new resources - are droppe + are dropped |
Fix proposed to branch: master /review. openstack. org/264340
Review: https:/