-
Notifications
You must be signed in to change notification settings - Fork 71
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
BUG: Rancher pod killed during backup restore when pruning is enabled #532
Comments
This seems unrelated to fleet. Not sure if this goes into the rancher repo or https://github.com/rancher/backup-restore-operator/issues While the restore seems to result in an inconsistent state, I'm wondering why this is fatal. I think it's related to this code path https://github.com/rancher/rancher/blob/release/v2.9/pkg/catalogv2/git/download.go#L78 |
Thanks for the tip. Full Logs here
|
ping @MKlimuszka - asking for help |
The Rancher pod going down during a prune is expected behaviour for an in-place restore. The This part of the short steps makes me think a migration:
As does this:
Overall my advice would be to follow the migration documentation to successfully restore the backup on the new cluster. This restore is done without rancher installed/running at all, and once successfully restored you start rancher. After which point you should create new backups for the rancher app running on this cluster. From a "In-place restore" vs "Migration" point of view, the primary question to ask is "what cluster did Rancher live on when this backup was taken?" If the answer is "a different one", then it's a migration; otherwise it can be an in-place restore. Even though the backup was successfully restored once upon migration, the backup was still created on a different cluster so should not be used for in-place restores. |
Thanks @mallardduck . |
Issue
While restoring a backup in Rancher with the exact same configuration as in the previous one, the rancher pod gets killed and Rancher UI dissappears as can be seen in the video
Screencast.from.25-07-24.16.40.15.webm
Step to reproduce (long way)
Short version to reproduce
Observed Behavior
Rancher pod gets deleted and although tries to recreate is never able to do so
Screencast.from.25-07-24.16.41.42.webm
Expected behavior
Pod should be able to recover well.
Gitjob is correctly deployed and active
Additional info
2.7-head
,2.8-head
and2.9-head
, however, it seemed not to affect Rancher2.7.6
(at least when tried for anoher issue)Testing environment
v1.27.10+k3s1
The text was updated successfully, but these errors were encountered: