-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: voltha-go-controller
-
Labels:None
-
Story Points:1
When VGC receives port delete event from voltha, VGC checks for ports only based on portNo. If a port at voltha has got a new portNo and voltha sends event to VGC to delete this port, VGC will not delete this port even though the port exists with same name. Since VGC only checks for portNo during deleting the port, it is skipping the delete of the port which was requested by voltha.
When VGC checks the ports based on name also, then the ports will get deleted from VGC even though there is a change of portNo at voltha.