I am attempting to restore Rancher (latest) from a backup tar (this is a fresh install) and getting the following error, I am running an HA Rancher install with K3s as its backing. Everything appears to be working correctly outside of this? Rancher will not come back up • Step1: I backed up Rancher • Step2: I deleted

testing-pci-cluster

• Step3: I restored from the backup I created in Step1

ERRO[2023/09/27 22:03:52] Error restoring namespaced resources [error restoring testing-pci-cluster of type <http://provisioning.cattle.io/v1|provisioning.cattle.io/v1>, Resource=clusters: restoreResource: err updating resource admission webhook "<http://rancher.cattle.io.clusters.provisioning.cattle.io|rancher.cattle.io.clusters.provisioning.cattle.io>" denied the request: creatorID annotation cannot be changed]

ERRO[2023/09/27 22:03:52] error syncing 'restore-qlmnh': handler restore: error restoring namespaced resources, check logs for exact error, requeuing

image.png

I cant seem to find a way to get my

local

cluster back online now, it appears to just keep being dead

Okay well i found the issue, not sure how to fix my cluster now. I guess i need to rebuild everything https://github.com/rancher/backup-restore-operator/issues/279#issuecomment-1585072910 Please ping me if you have a manual solution to fix this

Hello experts, I'm new to Rancher Desktop so this might be a naive question. I was using minikube as the local cluster manament tool for local development, and now switching to try Rancher Desktop. With minikube I can use

minikube dashboard

to bring up a web-gui dashboard. My question is with Rancher Desktop, is there similar dashboard and how I can do it? Any suggestions are welcome. Best regards.

oh, my previous question should go into rancher-desktop. Sorry for that.

I have harvester cluster running 1.1.2 with rancher 2.7.4 now the latest of both won’t work with older versions of either what is the recommended way to upgrade?

Hi all, We are running single node k3s. The disk usage was too high. After bit analysing I learn that snapshot folder under /var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs was consuming the most space.

root@ent-edge-metal-mum:/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs# du -smh * | sort -nr
3.8M	metadata.db
1.2T	snapshots

root@ent-edge-metal-mum:/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots# du -smh * | sort -nr | grep G
127G	10809
127G	10803
127G	10802
127G	10800
67G	14345
67G	14342
67G	14292
65G	14626
65G	14625
60G	10808
60G	10807
50G	11359
44G	14624
21G	16357

root@ent-edge-metal-mum:/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/10809/fs/app# du -smh * | sort -nr
127G	access.log

root@ent-edge-metal-mum:/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/10803/fs/app# du -smh * | sort -nr
127G	access.log

1. Can someone confirm why are the log files here are so big? And is there any way I can control the size of these log files under the /snapshots/NUM/fs/app folder? Any log rotation or truncate mechanism available here? 2. Is it safe to remove logs from these files?

Is it possible to get the kubeconfig of a RKE2 Guest Cluster using only the kubectl connected to rancher? That would be very nice

Team can someone help me with this info …in RKE cluster.yml file we mention all images to be downloaded with system_images attribute …but let’s say images already downloaded and I don’t want to download again …how can I do that ?

How I can use Continuous Delivery of Rancher on Rancher cluster itself?

Azure AD issue.png

Hello everyone good evening

Actually we have upgraded our rancher from 2.7.1 to 2.7.6 using helm package but we haven't noticed that our azure AD authentication secret key is expired without knowing that we have completed the rancher upgrade and rollout also we have done

Then we have tried with the new key but no use same issue we are getting can anyone let me know how can we resolve this issue

server error while authenticating:usersclient.baseclient.get():unexpected status 400 with odata error: Request_DataContractVersionMissing:The specified api-version is invalid.the value must exactly match a supported version Rancher.

This was the error

Hi, Could you enlighten me about rancher prime licensing? Rancher Prime is licensed by the number of nodes. Do I need to license all cluster nodes or just the ones running application workload? In a typical cluster I would have 3 master nodes running control plane and etcd with some infrastructure node running monitoring, logging, ingress, service mesh, storage and maybe some other workload, while the regular worker nodes would run the application.

I tried to find an "official" licensing guide but couldn't find any. Pointers to such documentation would be highly appreciated.

I had an RKE cluster that I imported into rancher. It shows up properly in the Rancher UI with all of the nodes, workloads, etc showing. The issue is that it shows as an "Imported" cluster in cluster management, and there are no configuration options. This was a cluster that was originally created with rancher, and "disassociated" with it. Is there any way on the back-end to enable the UI options (say with annotations) in the "edit cluster config" page? The existing cluster endpoints don't show up in the new kubectl file from the rancher UI, but they are still running on the cluster itself.

hello

is it possible to login to rancher using the rest api and the keycloakodicprovider?

i have tried using the v3-public/keyCloakOIDCProviders/keycloakoidc?action=loginwith the username and credentials as data binary but always take an authentication error

no problem using the gui

so i guess my oidc setup is ok

seems an api use related issue

Test

Hi All, I am running rke2 with rancher version 2.6.8. Under

cattle-logging-system

listing over 300

completed

pods like

rancher-logging-root-fluentd-configcheck-45909352

in completed state. For some reason pods are not disappearing. I do not see any option such

revisionHistoryLimit

to set as value in helm chart in order to remove completed pods automatically. Is there any reason why those pods are still there? Any proper solution for this? Thanks

Hello everyone , i have this error Could you help me?

@mammoth-dentist-35106 See this link where I helped a user a few days ago with the same issue <https://forums.rancher.com/t/migration-from-minikube-docker-to-rancher-podman-configuring-a-simple-local-cluster-etcd-error/41633/13?u=malcolmlewis1>