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
h
hundreds-hairdresser-46043
11/11/2022, 1:07 PMRKE2 upgrades observation. I did a cluster upgrade from v1.24.3+rke2r1 to v1.24.6+rke2r1 and now i see this and it does not go away. not sure why or how to fix it? There is no logs for this (the jobs) that i can visibly see
anyone have any clue about his?
c
creamy-pencil-82913
11/11/2022, 6:15 PMis your cluster out of resources ie you don’t have enough cores available to run everything?
you should be able to see why they are pending
s
sparse-fireman-14239
11/12/2022, 11:07 AMI assume you're hitting a bug in 1.24.6 where the CNI certificates are not renewed. It's fixed in 1.24.7
☝️ 2
h
hundreds-hairdresser-46043
11/14/2022, 7:03 AM@sparse-fireman-14239 I will do the same upgrade to 1.24.7 and see if the problem goes away - feedback to follow. Thank you for the hint
@creamy-pencil-82913 This is a clean cluster (no pods other then the core cluster and storage, they each have 4vCpu and 16gig memory) - so doubt it is a resource issue
@sparse-fireman-14239 cluster now running on v1.24.7+rke2r1. still have this problem. But now I am seeing the issue. Seems our taint setups is messing around example:
5 node(s) didn't match Pod's node affinity/selector. preemption: 0/8 nodes are available: 8 Preemption is not helpful for scheduling.
The strange thing here is - clean build works (no errors, everything deploys) , upgrades gives issue with the 3 jobs - and these 3 jobs then have issues with the taints.