after a tenant has deleted a resource, subsequent calls on new resources are dropped

Bug #1531597 reported by Adam Gandelman on 2016-01-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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

Fix proposed to branch: master

Changed in astara:
status: New → In Progress
Changed in astara:
milestone: none → mitaka-2

Submitter: Jenkins
Branch: master

commit 5fed2a704162d4277e6ab5e4e187c01ced440aeb
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: I5dcbeda7de240a693fc7a4944dd34a37b10d174b
    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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers