Comment 2 for bug 1827371

I can make a binary to delete the raft dir and rerun BootstrapRaft. I'll put in a check to indicate whether the log has entries with a --force for when we want to blow it away anyway.

It seems like sequence was:
* upgrading to 2.4
* check the raft dir doesn't already exist
* create the log and snapshot stores in raft dir
* call raft.BootstrapCluster which fails for some reason
* upgrade step fails and gets retried
* raft directory exists so the upgrade step thinks it's already bootstrapped and returns early.

Do you have logs that go far back enough to show the upgrade to 2.4? It would be good to know why the BootstrapCluster call fails.

At this point it's probably shutting the door after the horse has bolted, but I'll change the 2.4 upgrade step to use the check for a configuration entry used in the MigrateLegacyLeases step, rather than just checking for the raft directory.

I'll also change the MigrateLegacyLeases 2.5 step to run BootstrapCluster if it can't find the configuration entry. It's probably better than requiring people to run the emergency rebootstrap tool if we can detect the problem.