kytos-ng / mef_eline

Kytos NApp to create and manage point-to-point L2 circuits
https://kytos-ng.github.io/api/mef_eline.html
MIT License
0 stars 9 forks source link

Kytos 2023.2 fail to report status of the EVC correctly #537

Open italovalcy opened 1 month ago

italovalcy commented 1 month ago

Hi,

The EVC has an empty path but it is reporting as active and no log message about the EVC:

curl -X GET -u XXUSERXX -H 'Content-type: application/json' "https://xxxx/api/kytos/mef_eline/v2/evc/" > /tmp/evcs
> cat /tmp/evcs | jq -r '.["81f56a89c3164e"].current_path'
[]
> cat /tmp/evcs | jq -r '.["81f56a89c3164e"].active'
true
> cat /tmp/evcs | jq -r '.["81f56a89c3164e"].enabled'
true
> cat /tmp/evcs | jq -r '.["81f56a89c3164e"].primary_path|length'
4
> cat /tmp/evcs | jq -r '.["81f56a89c3164e"].backup_path|length'
4
italovalcy commented 1 month ago

Checked the EVC on the data-plane and it was really down

viniarck commented 1 month ago

That's definitely not good. @italovalcy lots of things going on, but later if you also have logs about the 81f56a89c3164e EVC, if you can also post some events that can be helpful.

Ktmi commented 5 days ago

This technically ties back to #437, as this is one of the things that should be caught by consistency check.