You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.
What happened?
When a client connects to the grpc proxy with an etcd cluster that has authentication enabled, new clients connecting after the auth token TTL has expired will not receive any watch events.
What did you expect to happen?
Clients connecting to the proxy after the first client's token expired should be able to establish their watch successfully and get events.
How can we reproduce it (as minimally and precisely as possible)?
Bug report criteria
What happened?
When a client connects to the grpc proxy with an etcd cluster that has authentication enabled, new clients connecting after the auth token TTL has expired will not receive any watch events.
What did you expect to happen?
Clients connecting to the proxy after the first client's token expired should be able to establish their watch successfully and get events.
How can we reproduce it (as minimally and precisely as possible)?
This test reproduces the issue
Anything else we need to know?
Proposed a potential fix in PR: #19033
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
The text was updated successfully, but these errors were encountered: