Deleting the tap-service port or tap-flow port doesn't clear the associated tap resources
Bug #1814937 reported by
Deepak Tiwari
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) |
Changed in tap-as-a-service: | |
importance: | Undecided → High |
Changed in tap-as-a-service: | |
milestone: | none → 5.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/635234
Review: https:/