mirror of
https://github.com/apache/cloudstack.git
synced 2025-10-26 08:42:29 +01:00
d893fb5b00
When agent loses connection with management server, the reconnection logic waits for any pending tasks to finish. However, when such tasks do finish they fail to send an `Answer` back to managements server. Therefore from a management server's perspective such pending operations are stuck in a FSM state and need manual removal or fixing. This is by design where management server's side cmd-answer request pattern is code/execution dependent, therefore even if the answer were to be sent when management server came back up (reconnects) the management server will fail to acknowledge and process the answer due to missing listeners or being in the exact state to handle answers. Historically, the Agent would wait to reconnect until the internal tasks complete but I found no reason why it should wait for reconnection at all. Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>