rancher: Create cluster, stuck in provisioning
Rancher versions: rancher/server: v2.0.0-beta1 rancher/agent: ??
Infrastructure Stack versions: healthcheck: ipsec: network-services: scheduler: kubernetes (if applicable):
Docker version: (docker version
,docker info
preferred)
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 3
Server Version: 18.03.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-1052-aws
Operating System: Ubuntu 16.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.858GiB
Name: ip-172-35-0-22
ID: GGHN:DTMK:ZPFT:FJU6:STC6:OWUF:3K5V:O5UC:CVIS:KMIH:3O7D:NFJ5
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Operating system and kernel: (cat /etc/os-release
, uname -r
preferred)
NAME=“Ubuntu”
VERSION=“16.04.4 LTS (Xenial Xerus)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 16.04.4 LTS”
VERSION_ID=“16.04”
HOME_URL=“http://www.ubuntu.com/”
SUPPORT_URL=“http://help.ubuntu.com/”
BUG_REPORT_URL=“http://bugs.launchpad.net/ubuntu/”
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB) Single Node
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
Results: This cluster is currently Provisioning; areas that interact directly with it will not be available until the API is ready.
Waiting for etcd and controlplane nodes to be registered
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 22 (6 by maintainers)
Dosen’t work for me 👎 What do you need to help me?
@MarcErdmann If re-using nodes, please clean them before re-using: https://gist.githubusercontent.com/superseb/2cf186726807a012af59a027cb41270d/raw/7cfbce916809e7b2474a73a3da367b1a7f4ac9cf/cleanup.sh
Then after, file a new issue with output of
docker logs --tail=all etcd
anddocker logs --tail=all kube-apiserver
. ThanksIt defaults to Ubuntu which uses ubuntu as SSH user. If you use the RancherOS AMI, this is stated on the section Amazon: