Comment 1 for bug 1527396

So after a rebalance, when a resource is mapped away from astara1 over to astara2, astara1 attempts to clean up its local state machines and remove management of the resource from its tenant resource manager. It does this by recycling the same code we use for deleting a resource, which flags the resource as having been deleted. Upon the next rebalance, astara1 attempts to recreate state machines for resource that now map to it, but creation doesn't happen because the resource was flagged as being deleted.