Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
c
creamy-pencil-82913
11/08/2022, 5:45 PMcheck the logs on the first node to see why it’s not ready yet
check rke2-server and rancher-system-agent logs
g
gifted-eye-43916
11/09/2022, 11:02 AMThe node is "Ready" in the cluster, but not through Cluster management
Firewalld is off, just like SELinux. And I run the nodes in same subnet under Proxmox
Issue was old RKE2 rpm's which were installed in the nodes. case closed