That may certainly work, but doesn't solve the issue.
Migrate of a M/S resource should switch the roles from M/S to S/M and not auto create a location constraint ban.

The DRBD M/S resources should be kept alive on both hosts to keep the replication going.
Only on a standby or a server down should the DRDB M/S be in non-replication and then when brought back online be in replication

How can I stop the auto creation of a location constraint ban?