A query for volume_move_status returning no results isn't something common to see. Today, the code has some retries around that call, but only for checking the current state of the operation, not to treat a 'no results' error. Do we have more evidences of this issue in recent releases? This can be an ONTAP issue that might be fixed already.
@ignazio, can you say which version of ONTAP you faced this issue?
A query for volume_move_status returning no results isn't something common to see. Today, the code has some retries around that call, but only for checking the current state of the operation, not to treat a 'no results' error. Do we have more evidences of this issue in recent releases? This can be an ONTAP issue that might be fixed already.
@ignazio, can you say which version of ONTAP you faced this issue?