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

[Bug] etcd snapshot-restore with etcd v3.5.9 fails due to missing /bin/sh in etcd container image, failure loop #45480

Open
todeb opened this issue May 14, 2024 · 0 comments
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release

Comments

@todeb
Copy link

todeb commented May 14, 2024

Rancher Server Setup

  • Rancher version: 2.7.10
  • Installation option (Docker install/Helm Chart): helm

Information about the Cluster

  • Kubernetes version: v1.25.16
  • Cluster Type (Local/Downstream): downstream
    • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):
  • Custom = Running a docker command on a node

User Information

  • What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
    admin

Describe the bug
related to this.
[Backport v2.7-Patch1] etcd snapshot-restore with etcd v3.5.9 fails due to missing /bin/sh in etcd container image

etcd-restore image seems to be in failure loop additionally to the above issue.

There are no documented steps how to stop this loop and no documented workaround for rancher to manually restore etcd from snapshot created by rancher if the image is failing or rancher functionality is not working.

To Reproduce
perform restore etcd snapshot with gui on rancher 2.7.10

Result
etcd restore failure loop

Expected Result
etcd restore will try once or max 3 times, fail, informing user about failure.

it should be documented way to stop the etcd-restore job and restoring etcd manually.

Screenshots

Additional context

@todeb todeb added the kind/bug Issues that are defects reported by users or that we know have reached a real release label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release
Projects
None yet
Development

No branches or pull requests

1 participant