I have tested the rc2 snap and the Xenial VMs are still showing IPV6 addresses: $ /snap/bin/juju status MODEL CONTROLLER CLOUD/REGION VERSION default vspherecontroller-rc2 vsphere/dc0 2.0-rc2.1 APP VERSION STATUS SCALE CHARM STORE REV OS NOTES easyrsa 3.0.1 active 1 easyrsa jujucharms 2 ubuntu elasticsearch active 2 elasticsearch jujucharms 19 ubuntu etcd 2.2.5 error 3 etcd jujucharms 13 ubuntu filebeat active 4 filebeat jujucharms 5 ubuntu flannel 0.6.1 active 4 flannel jujucharms 2 ubuntu kibana active 1 kibana jujucharms 15 ubuntu kubeapi-load-balancer 1.10.0 active 1 kubeapi-load-balancer jujucharms 2 ubuntu exposed kubernetes-master 1.4.0 active 1 kubernetes-master jujucharms 2 ubuntu kubernetes-worker 1.4.0 active 3 kubernetes-worker jujucharms 2 ubuntu exposed topbeat active 3 topbeat jujucharms 5 ubuntu UNIT WORKLOAD AGENT MACHINE PUBLIC-ADDRESS PORTS MESSAGE easyrsa/0 active idle 0 fe80::1 Certificate Authority connected. elasticsearch/0 active idle 1 10.245.62.35 9200/tcp Ready elasticsearch/1 active idle 2 10.245.62.36 9200/tcp Ready etcd/0 error idle 3 fe80::1 2379/tcp hook failed: "certificates-relation-changed" etcd/1 active idle 4 fe80::1 2379/tcp Healthy with 2 known peers. etcd/2 maintenance idle 5 fe80::1 Installing etcd from apt. kibana/0 active idle 6 10.245.62.40 80/tcp,9200/tcp ready kubeapi-load-balancer/0 active idle 7 fe80::1 443/tcp Loadbalancer ready. kubernetes-master/0 active idle 8 fe80::1 6443/tcp Kubernetes master running. filebeat/0 active idle fe80::1 Filebeat ready. flannel/0 active idle fe80::1 Flannel subnet 10.1.59.1/24 kubernetes-worker/0 active idle 9 fe80::1 80/tcp,443/tcp Kubernetes worker running. filebeat/3 active idle fe80::1 Filebeat ready. flannel/3 active idle fe80::1 Flannel subnet 10.1.3.1/24 topbeat/2 active idle fe80::1 Topbeat ready. kubernetes-worker/1 active idle 10 fe80::1 80/tcp,443/tcp Kubernetes worker running. filebeat/1 active idle fe80::1 Filebeat ready. flannel/1 active idle fe80::1 Flannel subnet 10.1.5.1/24 topbeat/0 active idle fe80::1 Topbeat ready. kubernetes-worker/2 active idle 11 fe80::1 80/tcp,443/tcp Kubernetes worker running. filebeat/2 active idle fe80::1 Filebeat ready. flannel/2 active idle fe80::1 Flannel subnet 10.1.89.1/24 topbeat/1 active idle fe80::1 Topbeat ready. MACHINE STATE DNS INS-ID SERIES AZ 0 started fe80::1 juju-7df5c0-0 xenial 1 started 10.245.62.35 juju-7df5c0-1 trusty 2 started 10.245.62.36 juju-7df5c0-2 trusty 3 started fe80::1 juju-7df5c0-3 xenial 4 started fe80::1 juju-7df5c0-4 xenial 5 started fe80::1 juju-7df5c0-5 xenial 6 started 10.245.62.40 juju-7df5c0-6 trusty 7 started fe80::1 juju-7df5c0-7 xenial 8 started fe80::1 juju-7df5c0-8 xenial 9 started fe80::1 juju-7df5c0-9 xenial 10 started fe80::1 juju-7df5c0-10 xenial 11 started fe80::1 juju-7df5c0-11 xenial RELATION PROVIDES CONSUMES TYPE certificates easyrsa kubeapi-load-balancer regular certificates easyrsa kubernetes-master regular certificates easyrsa kubernetes-worker regular peer elasticsearch elasticsearch peer elasticsearch elasticsearch filebeat regular rest elasticsearch kibana regular elasticsearch elasticsearch topbeat regular cluster etcd etcd peer etcd etcd flannel regular etcd etcd kubernetes-master regular juju-info filebeat kubernetes-master regular juju-info filebeat kubernetes-worker regular sdn-plugin flannel kubernetes-master regular sdn-plugin flannel kubernetes-worker regular loadbalancer kubeapi-load-balancer kubernetes-master regular kube-api-endpoint kubeapi-load-balancer kubernetes-worker regular beats-host kubernetes-master filebeat subordinate host kubernetes-master flannel subordinate kube-dns kubernetes-master kubernetes-worker regular beats-host kubernetes-worker filebeat subordinate host kubernetes-worker flannel subordinate beats-host kubernetes-worker topbeat subordinate I'm also not able to ssh into the bootstrap node: lmic@lmic-ThinkPad-T460s:~/snap/juju$ /snap/bin/juju ssh 0 ssh: connect to host fe80::1 port 22: Invalid argument