-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Enabling authentication in cluster will not synchronize this change to other members #3601
Comments
I could reproduce this. It is caused by the cache of enabled var in auth pkg. |
Thanks for the reply. I hope this issue get fixed soon. |
I can pick this up? |
@yichengq I use the same version, why don't I face this issue? |
@mitake Are you still working on this one? |
mitake
added a commit
to mitake/etcd
that referenced
this issue
Jan 26, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964
mitake
added a commit
to mitake/etcd
that referenced
this issue
Jan 26, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964
mitake
added a commit
to mitake/etcd
that referenced
this issue
Jan 26, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964
mitake
added a commit
to mitake/etcd
that referenced
this issue
Jan 26, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964
gyuho
pushed a commit
to gyuho/etcd
that referenced
this issue
Jan 27, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964 Conflicts: etcdserver/auth/auth.go
gyuho
pushed a commit
to gyuho/etcd
that referenced
this issue
Jan 27, 2016
This commit removes a flag that indicates auth is enabled or disabled because it doesn't have an invalidation mechanism. Fixes etcd-io#3601 and etcd-io#3964 Conflicts: etcdserver/auth/auth.go
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I built a 3-member cluster ( infra1, infra2, infra3 ) on three machines (dev01, dev02, dev03) with the latest stable version 2.2.0. Now I found that if I enable authentication on one member after creating root user, sometimes this change will be synchronize to other members, but sometimes it won't. And it seemed that using command line tool
etcdctl auth enable
has greater chance to trigger this bug than usingcurl
.Here's my steps:
curl
oretcdctl
, this change will be reflected on all the other members.etcdctl auth enable
on infra1, orcurl
, to enable authentication.curl http://dev02:2379/v2/auth/enable
andcurl http://dev03:2379/v2/auth/enable
to check the authentication status on infra2 and infra3. Sometime one or both will return{"enabled": false }
Thanks.
The text was updated successfully, but these errors were encountered: