Snapback operation from a Slave node always reports being successful on that node, even when it's in progress or resynchronization fails on Master

As per the CVM functionality, all operations are performed on the Master node, including those initiated on a Slave node that are then shipped to and performed on Master. When you run a task from Slave that takes a longer time to complete (for example, snapback), then the commands on Slave report that the operation was successful as soon as the task is submitted to Master. Therefore, the progress of such tasks should be monitored on Master as any failure during the task execution would not be reported back to the Slave.

This issue occurs when, for a cluster-shared volume, you perform the snapback operation from a Slave node. While the operation is still being performed on Master, on Slave it is reported as being successful. This happens even when the resynchronization operation fails. (3283523)

Workaround: There is no workaround for this issue.