Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
e
early-lifeguard-63817
01/03/2023, 1:41 PMg
gorgeous-television-46599
01/03/2023, 3:16 PMI just noticed that I have this as well on a k3s bare-metal cluster, that cluster has the "Rancher" repo in apps set to the wrong branch compared to the rancher version (I run rancher 2.7 while the branch is 2.6). Have you checked if you have a similar mismatched?
e
early-lifeguard-63817
01/05/2023, 2:21 PMtbh I'm not sure how this sync even works
I mean.. is it syncing the repos to rancher server.. or to a PVC in the managed cluster.. or where..
I deleted the Rancher repo and recreated it, same "In Progress" status...
this is the only cluster where I have this issue.. weird.