EVC with dynamic path is never activated if links was not enable when created

[italovalcy]

Hi,

If you create an EVC with a dynamic path and all possible paths are with the links disabled, then the EVC will never be activated even if you enable all the links later.

Steps to reproduce:

1. Create a topology and start Kytos (without enable-all option):

kytosd
mn --topo linear,3 --controller=remote,ip=127.0.0.1

2. Create an EVC with dynamic path:

curl -s -X POST -d '{"uni_z": {"tag": {"value": 110, "tag_type": 1}, "interface_id": "00:00:00:00:00:00:00:03:1"}, "uni_a": {"tag": {"value": 110, "tag_type": 1}, "interface_id": "00:00:00:00:00:00:00:01:1"}, "enabled": true, "name": "Vlan110_Test2", "dynamic_backup_path": true}' -H 'Content-Type: application/json' http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/

3. Enable all the switches, interfaces and links:

for s in $(curl -s http://127.0.0.1:8181/api/kytos/topology/v3/switches | jq -r '.switches[].id'); do curl -X POST -H 'Content-Type: application/json' http://127.0.0.1:8181/api/kytos/topology/v3/switches/$s/enable; curl -X POST -H 'Content-Type: application/json' http://127.0.0.1:8181/api/kytos/topology/v3/interfaces/switch/$s/enable; done

for l in $(curl -s http://127.0.0.1:8181/api/kytos/topology/v3/links | jq -r '.links[].id'); do curl -X POST -H 'Content-Type: application/json' http://127.0.0.1:8181/api/kytos/topology/v3/links/$l/enable; done

4. Check the EVC status:

curl -s http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/  | jq -r '.[].active'

Expected result:

• the EVC should be active when the links get activated

Actual result:

• the EVC never gets active

Workaround: disable and enable the EVC:

curl -s -X PATCH -H "Content-Type: application/json" -d '{"enable": false}' http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/662c1a58b2da41e4

curl -s -X PATCH -H "Content-Type: application/json" -d '{"enable": true}' http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/662c1a58b2da41e4

[ArturoQuintana]

This issue has been fixed by the contribution done on PR #157
It has been tested following the steps sequences provided above, and it has not been detected errors.