-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Auth failed with error "auth: revision in header is old" #13976
Comments
Hi @ahrtr ,
So we suspect that RoleRevokePermission method in store.go file of etcd code base is having some problem which is failing to apply request. Thanks, |
cc @mitake Please format the log using |
@rahulbapumore I guess this issue was fixed in #13308 Can you reproduce it in the latest main branch? |
@ahrtr sorry for confusion, I was the one who formatted the code before :P |
Thanks @mitake , probably it makes sense to backport the fix to 3.4 as well? |
@ahrtr Yeah, probably there are some requirements. Let me open a PR for backporting. |
Hi @ahrtr , Thanks, |
Hi @mitake , Thanks, |
@rahulbapumore the change will be included in the next stable release, v3.4.19 (#14017). I think @hexfusion is maintaining stable releases of v3.4, do you have a plan for the next release? |
Please read v3.5-data-inconsistency.md#detection |
Hi @ahrtr , Thanks, |
Hi @ahrtr , Thanks, |
Hi @ahrtr , Thanks, |
I meet data inconsistency in 3.4.9. the leader's revsion is a lot behind, and memory is much smaller than followers. the revision diff show as below: the request inbound rate: peer network: mvcc metrics: the log of leader show as below:
|
Hi @ahrtr , Thanks, |
We are still working on it. See issues/14074 and issues/13912. Instead of passively waiting on the release, please feel free to proactively help to resolve the test issue in 3.4. |
Since the PR have already been backported to 3.4, so closing this issue. |
Hi @ahrtr , Thanks, |
etcd version
3.4.16
Background
The original issue is 13503. There is a long back-and-forth conversation, but not much progress, so I raise a new issue to get the latest error message included.
There are 3 members in the etcd cluster, and the original version was 3.3.11. In the beginning, the users saw the data inconsistency issue, which could be caused by 11651. The issue was fixed in 3.3.21, 3.4.8 and 3.5.0. So the user upgraded to 3.4.16, and then see the error "
auth: revision in header is old
" (see detailed log below).Please refer to the following two files to get the detailed info on how the user configures & deploys the etcd cluster,
configmap.txt
statefulset.txt
Help wanted
If you run into the same issue, please provide the etcd version & detailed steps to reproduce this issue. Thanks.
It also would be helpful if anyone can reproduce this issue in 3.5 and main branch.
Error message
The text was updated successfully, but these errors were encountered: