-
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
http health check bug fixes #16697
http health check bug fixes #16697
Conversation
195b585
to
a2b57bd
Compare
Couple of high level questions To clarify this PR makes etcd healthcheck work when authorization is enabled. Without it checking health is short circuited by permission denied error and doesn't validate reading db at all. Is this correct? Do you plan to backport this change? Even though the check is not useful, I would prefer to avoid making a change in old releases. Better to ask users to migrate to new /health endpoint then just surprize them with the change. How have you tested the change? Have you considered testing it manually that everything works? Adding an e2e tests or verifying that this feature is covered by testing would also be appreciated. |
lgtm |
Correct.
No plan to backport this change. I agree we should ask users to migrate to
Yeah, test is in progress.. refer #16698 |
My understanding is the test in the PR should all pass on top of this PR. Pls verify that and feedback the result, thx. |
dc1474c
to
a8a74eb
Compare
Signed-off-by: Chao Chen <[email protected]>
a8a74eb
to
c25f1df
Compare
Hi @chaochn47 the change looks good. but it seems that the change has been covered by #16651.... |
Yeah, #16651 This PR is the bug fix backported to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Part of #16007
Discovered by reviewing #16651
@siyuanfoundation @serathius