adding a node to a cluster which has the same otpCookie causes issues ( happens when vm is cloned or created from an AMI/VM_Template where couchbase was already installed)

I'm seeing intermittent problems when building a cluster of Membase servers. Sometimes adding an additional server to a cluster will cause another server to be marked as unhealthy. Other times the additional server will function correctly but all others will appear to be in setup mode. This only happens some times, so it's tricky to nail down properly.

Steps to reproduce this are in this forum thread: http://www.couchbase.org/forums/thread/server-marked-unhealthy-after-adding-additional-server-cluster

In the most recent test run, I spun up 3 m2.xlarge instances as described in the forum post. On adding the third server to the cluster (from the admin web interface on the first server), the admin interface refreshed and showed the setup dialog. When I browsed to the second server it was also in setup mode. The third server was configured correctly and appeared to be running in its own cluster of one machine. I've attached the output from /logs on all three machines.

(Forgive me if I have the wrong component selected, I'm not quite sure which one is causing me to see this issue.)