Bootstrap fails in AWS - Other bootstrapping/leaving/moving nodes detected

[takism1]

I created a 3-node cluster in AWS using the latest AMI (ami-711ca91a) specifying the following in User Action --opscenter no --opscenterip <ip of my oc> --clustername test --totalnodes 3 --version community --release 2.1.11

Then I tried to add a node to this cluster by creating a 1-node cluster using the same AMI but passing the following to User Actions: --opscenter no --opscenterip <ip of my oc> --bootstrap true --seeds <internal ip of first node in cluster> --clustername test --totalnodes 1 --version community --release 2.1.11.

Cassandra fails to start on the new node and I see this exception in its log:

java.lang.UnsupportedOperationException: Other bootstrapping/leaving/moving nodes detected, cannot bootstrap while cassandra.consistent.rangemovement is true

This seems to be consistently happening when I try adding a node even though in nodetool I see all existing nodes as having Normal state and it's been much longer than 2 minutes (as indicated here) since I last tried to add a node. Restarting cassandra on the new node usually fixes it (although occasionally I see another exception that it cannot gossip with seed nodes which gets fixed if I restart cassandra on the seed node and then restart it on the new node).

[mlococo]

This is not a path that I regularly test and I'm not sure what's going on here. I'll leave the issue open for now and perhaps another community member will chime in. If you do get to the bottom of the issue, please follow-up with your analysis.