after a tenant has deleted a resource, subsequent calls on new resources are dropped
Bug #1531597 reported by
Adam Gandelman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Astara |
Fix Released
|
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: | |
milestone: | none → mitaka-2 |
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 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/264340
Review: https:/