CoreOS won't cluster past three nodes and won't allow fleetctl to tunnel in

December 31, 2015 637 views
Clustering DigitalOcean

DO Support verified both issues and said they were CoreOS issues and they couldn't help.

Here is my use case from the ticket Support verified...

I destroyed them all, did a new without a size, created 5 new droplets using this yml


# generate a new token for each unique cluster from 
# specify the initial size of your cluster with ?size=X
# multi-region and multi-cloud deployments need to use $public_ipv4
advertise-client-urls: http://$private_ipv4:2379,http://$private_ipv4:4001
initial-advertise-peer-urls: http://$private_ipv4:2380
# listen on both the official ports and the legacy ports
# legacy ports can be omitted if your application doesn't depend on them
listen-peer-urls: http://$private_ipv4:2380
- name: etcd2.service
command: start
- name: fleet.service
command: start
- name: flanneld.service
- name: 50-network-config.conf
content: |
ExecStartPre=/usr/bin/etcdctl set / '{ "Network": "" }'
command: start

and fleet-ctl list-machines still only sees three of them.

core@ssr-01 ~ $ fleetctl list-machines
4cd69ff8... -
4cdba3ea... -
92e76f2b... -

I tried using a tunnel to remote into one of the CoreOS machines that did get etcd'd but it fails...

JVRs-MacBookPro:~ jvr$ export FLEETCTL_TUNNEL=
JVRs-MacBookPro:~ jvr$ fleetctl list-machines
The authenticity of host '' can't be established.
RSA key fingerprint is fe:96:a8:c0:60:e5:7c:36:7c:7a:1e:de:e0:53:45:b1.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '' (RSA) to the list of known hosts.
Unable to initialize client: failed initializing SSH client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

DO Support said it is a problem in the CoreOS and there is nothing they can do.

Any ideas on a work around for either of these issues? I'm using 835.9.0 (stable) which I assumed was the safe choice but Im wondering if I should use Windows Vista instead! :-)

I wonder if it is telling that DO doesnt provide a CoreOS tag in the set below. But I am forced to select one


Be the first one to answer this question.