Document fix issue with Consul cluster creation on DO
Additionally, if you try and create a cluster without specifying
bind_addr, then fix the issue. The nodes will still try and use the unroutable private IP address due to it being in their cached copy of the data.
The current workaround is to remove the
/var/opt/gitlab/consul/data directory, and restart consul. This should be added to the troubleshooting document until a proper fix can be found.