Closed Mythobeast closed 3 years ago
The agents are a part of Rancher, please file this using https://github.com/rancher/rancher/issues/new. Please search through existing issues first and use https://rancher.com/docs/rancher/v2.x/en/troubleshooting/, based on what is provided the overlay network is not being created successfully which could be due to (host) firewall or possible multi homed hosts and wrong interface auto detection.
When the cluster tries to start up, the kube-apiserver instances spam the following lines, over and over.
Rancher is running on docker on 10.90.48.101, nodes are on ~.102, ~.103, and ~.111
Any clue to get me going would be welcome.
RKE version: rancher/hyperkube:v1.19.3-rancher1
Docker version: (
docker version
,docker info
preferred) Docker version 19.03.13, build 4484c46d9dOperating system and kernel: (
cat /etc/os-release
,uname -r
preferred) 3.10.0-1127.19.1.el7.x86_64Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) Bare-metal
cluster.yml file:
Steps to Reproduce: Provision servers with Centos-7 Create cluster with default values Add nodes to cluster
Results: Nodes register, but cluster stays in state Cluster health check failed: cluster agent is not ready