Comment 3 for bug 2016868

Initial comment, RE:

So we end up going from:
{
  0: true,
  1: true,
  2: true,
}

to
{
  1: true,
  2: false,
}

---

If machine 0 is removed and is the mongo primary, I think we are supposed to call "StepDownPrimary()" and then re-evaluate things. I would hope that this would then result in going from:
{
  1: true,
  2: true,
}

to
{
  1: true,
  2: false,
}

which is only one change. So maybe the logic to evaluate the new desired replicaset config has a bug such that it doesn't set the "stepDownPrimary" flag when it should.