telemetry_int has been validating that flows exist when trying to enable INT for correctness, this is validation to ensure that the expected flows by cookies would be found, however, there's a corner case:
mef_eline can have an inactive EVC temporarily, where it would have no flows since mef_eline always clean up the flows, so trying to enable INT should also be supported in this case. It won't install any flows, however in subsequent network convergence like link up then it would redeploy. Since now telemetry int has been supporting other network convergence, it's time to lift this restriction here, so if an inactive EVC has no flows the INT metadata should be set, but then with telemetry metadata status "DOWN".
How to reproduce
Try to enable INT on an inactive EVC (currently without any paths) returns 404
{
"description": "EVC 9461d30603ae44 flows not found",
"code": 404
}
telemetry_int
has been validating that flows exist when trying to enable INT for correctness, this is validation to ensure that the expected flows by cookies would be found, however, there's a corner case:mef_eline
can have an inactive EVC temporarily, where it would have no flows since mef_eline always clean up the flows, so trying to enable INT should also be supported in this case. It won't install any flows, however in subsequent network convergence like link up then it would redeploy. Since now telemetry int has been supporting other network convergence, it's time to lift this restriction here, so if an inactive EVC has no flows the INT metadata should be set, but then with telemetry metadata status "DOWN".How to reproduce