There is a misleading message when doing a rerouting:
"action": "Failed to reroute the flow",
"details": "Reroute is unsuccessful. Couldn't find new path(s)"
but at the same time rerouting could actually bring the flow from DOWN to UP. This message actually means that new paths were not found, but this might be correct and the flow goes UP using the old paths that were unavailable before, but can be used now.
Steps to reproduce:
- Create a flow with any parameters, make sure the flow status is UP
- Take down all ports on one of the switches (for example by using the switch controller
/switches/00:00:00:00:00:00:00:01/port/1/config with a body {"status":"DOWN"}. Make sure the flow is DOWN
- Bring one of the ports UP, so that the flow could use it. Make sure the flow is UP again
- Navigate to the flow's history, find the automatic reroute event:
Actual result: one of the actions says: Failed to reroute the flow (other action says "action": "The flow status was reverted to UP")
Expected result: the message does not imply that a reroute was unsuccessful if it is not the case.
There is a misleading message when doing a rerouting:
but at the same time rerouting could actually bring the flow from DOWN to UP. This message actually means that new paths were not found, but this might be correct and the flow goes UP using the old paths that were unavailable before, but can be used now.
Steps to reproduce:
/switches/00:00:00:00:00:00:00:01/port/1/configwith a body{"status":"DOWN"}. Make sure the flow is DOWNActual result: one of the actions says:
Failed to reroute the flow(other action says"action": "The flow status was reverted to UP")Expected result: the message does not imply that a reroute was unsuccessful if it is not the case.