telstra/open-kilda

Ha-Flow: Unsuccessful reroute: Both sub-flows are stuck in 'In_Progress' status

yuliiamir opened this issue · 0 comments

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",

"ha_flow_id": "19Jan190850_833_galangal6854_haflow",
  "status": "Up",
  "shared_endpoint": {
  ...
  },
  "sub_flows": [
    {
      "flow_id": "19Jan190850_833_galangal6854_haflow-b",
      "endpoint": {
        ...
      },
      "status": "In progress",
      "description": null,
      "time_create": "2024-01-19T18:08:52.847Z",
      "time_update": "2024-01-19T18:09:05.742Z",
      "forward_latency": 5000000,
      "reverse_latency": 7000000,
      "latency_last_modified_time": "2024-01-19T18:09:01.353Z"
    },
    {
      "flow_id": "19Jan190850_833_galangal6854_haflow-a",
      "endpoint": {
       ...
      },
      "status": "In progress",
      "description": null,
      "time_create": "2024-01-19T18:08:52.847Z",
      "time_update": "2024-01-19T18:09:05.742Z",
      "forward_latency": 3000000,
      "reverse_latency": 5000000,
      "latency_last_modified_time": "2024-01-19T18:09:01.538Z"
    }
  ]

KibanaLogs

haFlowDetailsAfterUnsuccessfulReroute.json

haFlowHistory.json