You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deleting an EVC, mef_eline makes a request to delete flows, but if the concurrency limit is achieved flow_manager will return 503 as expected. In this case mef_eline mef_eline was also returning a successful request response incorrectly.
How to reproduce:
Create 100 EVCs and try to delete them at once concurrently.
Potential solution(s) to discuss:
Handle and propagate the return back without deleting the EVC
Use event based flows deletions instead of a request and make sure that no out of order events would be problematic
This is issue is very related to issue #476. If this bug happens and EVCs are created, kytos will eventually create duplicated flows. If we deal with leftover flows and assure the complete deletion of them, we can close both issues.
Problem:
mef_eline
makes a request to delete flows, but if the concurrency limit is achieved flow_manager will return 503 as expected. In this casemef_eline
mef_eline was also returning a successful request response incorrectly.How to reproduce:
Potential solution(s) to discuss:
Here's a full example of flows of an EVC that has been deleted but still has installed flows:
The text was updated successfully, but these errors were encountered: