Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues restoring local cluster from backup operator #598

Closed
gthibaultd opened this issue Oct 14, 2024 · 1 comment
Closed

Issues restoring local cluster from backup operator #598

gthibaultd opened this issue Oct 14, 2024 · 1 comment

Comments

@gthibaultd
Copy link

Rancher Setup

Rancher version:
Rancher v2.9.2
Installation option (Docker install/Helm Chart):
Helm Chart on GKE cluster with 3 nodes
Kubernetes Version and Engine:
Client Version: v1.30.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.5-gke.1014001
Rancher-backup version: 104.0.1+up5.0.1

Describe the bug

When we try a rancher restoration from GCP S3 we always get this error :

ERRO[2024/10/10 14:27:16] Error restoring resource cluster-01 of type provisioning.cattle.io/v1, Resource=clusters: restoreResource: err updating resource admission webhook "rancher.cattle.io.clusters.provisioning.cattle.io" denied the request: creatorID annotation cannot be changed

To Reproduce

1 - Install rancher through Helm.
2 - Install app Backup on rancher markeplace.
3 - Add ubuntu node with rancher registration command.
4 - Create a s3 backup (works fine)
5 - Delete the local rancher to simulate a rancher server loss.
6 - Do step 1 & 2
7 - Create a restore with the fresh new file on s3 with the same access as the restore one. (https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher)

Expected behavior

Have a Working rancher and have the ubuntu cluster attach itself automatically. (It was a kind of restore test)

Additionnal context

We systematically have this error. To restore it, we followed this procedure: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher
We have seen that this error exists in the documentation. (https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher#known-issues) But if we have a large number of clusters, it's not practical to delete all the objects at once. Have we missed something for the restore to go smoothly?

@gthibaultd
Copy link
Author

Find the issue. For this case we don't need to use Restore documentation but the Migration One.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant