-
-
Notifications
You must be signed in to change notification settings - Fork 231
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]: Restore script not working #625
Comments
i suspect whether we have to restore the |
Here is the scripts that were used : https://github.com/OT-CONTAINER-KIT/redis-operator/tree/master/scripts Example manifest to be used are here https://github.com/OT-CONTAINER-KIT/redis-operator/tree/master/example/v1beta2/backup_restore |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
What version of redis operator are you using?
Redis-operator logs :
{"level":"error","ts":1694770207.2931252,"logger":"controller_redis","msg":"Could not execute command","Request.RedisManager.Namespace":"default","Request.RedisManager.Name":"redis-cluster","Command":["redis-cli","--cluster","create","redis-cluster-leader-0.redis-cluster-leader-headless.default.svc:6379","redis-cluster-leader-1.redis-cluster-leader-headless.default.svc:6379","redis-cluster-leader-2.redis-cluster-leader-headless.default.svc:6379","--cluster-yes"],"Output":"[ERR] Node redis-cluster-leader-0.redis-cluster-leader-headless.default.svc:6379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.\n","Error":"","error":"command terminated with exit code 1","stacktrace":"github.com/OT-CONTAINER-KIT/redis-operator/k8sutils.ExecuteRedisClusterCommand\n\t/workspace/k8sutils/redis.go:115\ngithub.com/OT-CONTAINER-KIT/redis-operator/controllers.(*RedisClusterReconciler).Reconcile\n\t/workspace/controllers/rediscluster_controller.go:183\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:114\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:311\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:227"}
redis-operator version: v0.15.1
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
Tried to restore redis-cluster
From script provided here : https://github.com/OT-CONTAINER-KIT/redis-operator/tree/master/example/v1beta2/backup_restore
What did you expect to see?
Restore should have been done properly
What did you see instead?
The text was updated successfully, but these errors were encountered: