-
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
Flaky integration test case TestV3AuthWithLeaseRevokeWithRootJWT
#16475
Comments
I think the reason for the failure is that the JWT has expired when server sending etcd/server/etcdserver/server.go Lines 875 to 886 in 2763392
The log shows: logger.go:130: 2023-08-25T14:06:59.695Z DEBUG client retrying of unary invoker {"target": "etcd-endpoints://0xc000302780/localhost:m0", "method": "/etcdserverpb.Lease/LeaseGrant", "attempt": 0}
logger.go:130: 2023-08-25T14:06:59.702Z DEBUG client retrying of unary invoker {"target": "etcd-endpoints://0xc000302780/localhost:m0", "method": "/etcdserverpb.KV/Put", "attempt": 0}
logger.go:130: 2023-08-25T14:07:02.013Z WARN m0 failed to parse a JWT token {"member": "m0", "error": "Token is expired"}
logger.go:130: 2023-08-25T14:07:02.013Z WARN m0 invalid auth token {"member": "m0", "token": "***"}
logger.go:130: 2023-08-25T14:07:02.013Z WARN m0 failed to revoke lease {"member": "m0", "lease-id": "61048a2d0509a20b", "error": "auth: invalid auth token"} Since the lease ttl is 2, It would expired at 2023-08-25T14:07:01.695Z. And I believe the server called Lines 101 to 106 in 2763392
I have run this test on my devbox and usually it only takes less than 10ms to send |
@YaoC would you please to send patch to fix this? Thanks! |
Sure, I'll fix it. |
same happened on the 3.5 branch PR here:
|
Which github workflows are flaking?
test (linux-amd64-integration-1-cpu)
Which tests are flaking?
TestV3AuthWithLeaseRevokeWithRootJWT
Github Action link
https://github.com/etcd-io/etcd/actions/runs/5976797722/job/16215421678?pr=16472
Reason for failure (if possible)
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: