Former singleton provider node leaving cluster after re-election causes another re-election

With a random election policy, this situation is likely to happen:
1. After a topology change, new singleton provider is elected
2. Former singleton provider undeploys the singleton application, which causes it to leave a cluster for a while
3. This topology change triggers another election
4. Loop continues