Skip to content

Add a new workflow path in rerouting FSMs to skip rerouting#5526

Open
dmitrii-beliakov wants to merge 1 commit intodevelopfrom
fix/history_reroute
Open

Add a new workflow path in rerouting FSMs to skip rerouting#5526
dmitrii-beliakov wants to merge 1 commit intodevelopfrom
fix/history_reroute

Conversation

@dmitrii-beliakov
Copy link
Copy Markdown
Collaborator

@dmitrii-beliakov dmitrii-beliakov commented Dec 21, 2023

This PR introduces a new behavior when a flow or HA-flow transits from DOWN to UP state and automatic reroute is invoked. In case, when there is only one path which goes down and then up, automatic reroute cannot find a new better path, but at the same time it is not needed because the flow is working using the old paths that are now ok. In this case the reroute is not needed and skipped. In the history we can see messages about the skipped rerouting, so that we can distinguish it with a rerouting that allocates new resources.
The message in the history that reroute is unsuccessful in this case is now removed.

closes #5291

@dmitrii-beliakov dmitrii-beliakov marked this pull request as ready for review January 3, 2024 19:30
…s not needed because the flow is already in the UP state.
@dmitrii-beliakov dmitrii-beliakov removed their assignment May 7, 2024
@dmitrii-beliakov
Copy link
Copy Markdown
Collaborator Author

It's been some time ago, I think there was a problem because some of the tests relies on the history outcome, which has changed. Please double check the test failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A misleading message in the flow history when rerouting

2 participants