Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A misleading message in the flow history when rerouting #5291

Open
dmitrii-beliakov opened this issue Jul 18, 2023 · 0 comments · May be fixed by #5526
Open

A misleading message in the flow history when rerouting #5291

dmitrii-beliakov opened this issue Jul 18, 2023 · 0 comments · May be fixed by #5526

Comments

@dmitrii-beliakov
Copy link
Collaborator

dmitrii-beliakov commented Jul 18, 2023

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:

  1. Create a flow with any parameters, make sure the flow status is UP
  2. 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
  3. Bring one of the ports UP, so that the flow could use it. Make sure the flow is UP again
  4. 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.
@dmitrii-beliakov dmitrii-beliakov changed the title Misleading message in the flow history when doing a reroute A misleading message in the flow history when rerouting Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant