Skip to content
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

Backport https://github.com/etcd-io/etcd/pull/19139 to 3.5 and 3.4 #19150

Open
4 tasks
ahrtr opened this issue Jan 9, 2025 · 2 comments
Open
4 tasks

Backport https://github.com/etcd-io/etcd/pull/19139 to 3.5 and 3.4 #19150

ahrtr opened this issue Jan 9, 2025 · 2 comments
Assignees
Labels

Comments

@ahrtr
Copy link
Member

ahrtr commented Jan 9, 2025

Bug report criteria

What happened?

See #19139

What did you expect to happen?

.

How can we reproduce it (as minimally and precisely as possible)?

.

Anything else we need to know?

No response

Etcd version (please run commands below)

$ etcd --version
# paste output here

$ etcdctl version
# paste output here

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)

$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

No response

@ahrtr ahrtr added the type/bug label Jan 9, 2025
@joshuazh-x
Copy link
Contributor

I’ll back port this to 3.5 & 3.4.

@ahrtr
Copy link
Member Author

ahrtr commented Jan 9, 2025

/assign @joshuazh-x

thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants