You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue has been caught during execution of manual HA-Flow reroute request when the current path is the best (reroute:false).
TC: Not able to reroute to a path with not enough bandwidth available
Both sub-flow are in the 'In_Progress' status when the Ha-Flow is in 'Up' after unsuccessful reroute.
Reroute event :
"clazz": "org.openkilda.messaging.payload.history.HaFlowHistoryEntry",
"ha_flow_id": "19Jan190850_833_galangal6854_haflow",
"time": 1705687745.672,
"timestamp_iso": "2024-01-19T18:09:05.672Z",
"actor": "AUTO",
"action": "HA-Flow reroute",
The issue has been caught during execution of manual HA-Flow reroute request when the current path is the best (reroute:false).
TC:
Not able to reroute to a path with not enough bandwidth available
Both sub-flow are in the 'In_Progress' status when the Ha-Flow is in 'Up' after unsuccessful reroute.
Reroute event :
"clazz": "org.openkilda.messaging.payload.history.HaFlowHistoryEntry",
"ha_flow_id": "19Jan190850_833_galangal6854_haflow",
"time": 1705687745.672,
"timestamp_iso": "2024-01-19T18:09:05.672Z",
"actor": "AUTO",
"action": "HA-Flow reroute",
haFlowDetailsAfterUnsuccessfulReroute.json
haFlowHistory.json
The text was updated successfully, but these errors were encountered: