Deleting the tap-service port or tap-flow port doesn't clear the associated tap resources

Bug #1814937 reported by Deepak Tiwari
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tap-as-a-service
Fix Released
High
Deepak Tiwari

Bug Description

If we delete the tap-service port or tap-flow port (without first deleting the associated tap resource) then the associated tap resource keeps hanging, even the port resource does not get cleared properly as tap resource still keep referring to it, so port uuid is not released.

Changed in tap-as-a-service:
assignee: nobody → Deepak Tiwari (deepaktiwari)
status: New → In Progress
Changed in tap-as-a-service:
assignee: Deepak Tiwari (deepaktiwari) → nobody
assignee: nobody → Deepak Tiwari (deepaktiwari)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tap-as-a-service (master)

Fix proposed to branch: master
Review: https://review.openstack.org/635234

Revision history for this message
Deepak Tiwari (deepak.tiwari) wrote :
Changed in tap-as-a-service:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tap-as-a-service (master)

Reviewed: https://review.openstack.org/635234
Committed: https://git.openstack.org/cgit/openstack/tap-as-a-service/commit/?id=080ef1661f5a84b71d0954899e6bad34d3035540
Submitter: Zuul
Branch: master

commit 080ef1661f5a84b71d0954899e6bad34d3035540
Author: Deepak Tiwari <email address hidden>
Date: Wed Feb 6 11:57:12 2019 -0600

    Clear associated tap resources on port delete

    Change-Id: Ifdaa08734825dd5fe9ded2ce13d16cad699d0737
    Closes-Bug: #1814937

Changed in tap-as-a-service:
status: In Progress → Fix Released
Changed in tap-as-a-service:
milestone: none → 5.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.