-
Notifications
You must be signed in to change notification settings - Fork 111
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
Error: etcdserver: member not found, after upgrading helm chart etcd replicas 1 to 3 #1659
Comments
I don't think this will work automatically. |
did also a test scalling to 2 replicas, in that case etcd-0 was healthy but etcd-1 show errors:
Also after 1st case when I rollback from 3 to 1 replica for etcd. etcd-0 lost its all data. Fortunately I made a snapshot of etcd before and restored it. In 2nd case when scalling from 1 to 2 and rollback from 2 to 1. etcd-0 was healthy entire time so data was kept. |
I haven't had the time yet, but I wonder if the etcd-operator would help here? #1630 |
openebs/mayastor-extensions@6a2bf49
Describe the bug
After upgrading chart with mayastor.etcd.replicaCount=3 from 1.
etcd-0 member crashloopbackoff with log:
other new deployed etcd members logs:
Current helm values:
Previous helm values:
To Reproduce
Expected behavior
all etcd members are healthy
Screenshots
If applicable, add screenshots to help explain your problem.
OS info (please complete the following information):
openebs.io/version: 2.6.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: