[3.5] bugfix: register of walWriteSec

[andyxning]

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

cherry-pick #18164 to release-3.5

/cc @ivanvc

[k8s-ci-robot]

Hi @andyxning. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ivanvc]

/ok-to-test

[ahrtr]

Good catch!

Thank you.

[ivanvc]

LGTM. Thanks, @andyxning. Could you open a PR to update 3.5's CHANGELOG with this bug fix as pointed out by Benjamin? Thanks again.

[andyxning]

@ivanvc This is a bugfix to adding support for walWriteSec and walWriteSec was added in v3.5. There is no need to update in the changelog, imho.

[ivanvc]

@ivanvc This is a bugfix to adding support for walWriteSec and walWriteSec was added in v3.5. There is no need to update in the changelog, imho.

Yes, but at least 3.5.14 was released with this bug. I think that's why we need the release note, and why Benjamin requested it.

[ivanvc]

/retitle [3.5] bugfix: register of walWriteSec