Automated cherry pick of #124026: etcd: build etcd image of v3.5.13 #124027: etcd: update to v3.5.13

[liangyuanpeng]

Cherry pick of #124026 #124027 on release-1.29.

#124026: etcd: build etcd image of v3.5.13
#124027: etcd: update to v3.5.13

For details on the cherry pick process, see the cherry pick requests page.

etcd: Update to v3.5.13

[k8s-ci-robot]

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers

(This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.)

For details on the patch release process and schedule, see the Patch Releases page.

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/test-infra repository.

[k8s-ci-robot]

Hi @liangyuanpeng. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[liangyuanpeng]

/assign @serathius @dims

[dims]

/ok-to-test

[liangyuanpeng]

/remove-sig api-machinery

[dims]

/approve
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2a39368bd0ad5147e0f7eedccfd6b7ca1a193f80

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, liangyuanpeng

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• build/OWNERS [dims]
• cluster/gce/OWNERS [dims]
• cluster/images/etcd/OWNERS [dims]
• cmd/kubeadm/OWNERS [dims]
• hack/OWNERS [dims]
• staging/src/k8s.io/sample-apiserver/OWNERS [dims]
• test/e2e/framework/OWNERS [dims]
• test/utils/image/OWNERS [dims]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[serathius]

/retest

[liangyuanpeng]

Failed logs:

 STEP: Destroying namespace "loadbalancers-905" for this suite. @ 04/27/24 09:16:37.543
  << Timeline
  [FAILED] HTTP service 172.18.0.6:81 not rejected: timed out waiting for the condition
  In [It] at: k8s.io/kubernetes/test/e2e/network/service.go:454 @ 04/27/24 09:16:37.264
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
Summarizing 2 Failures:
  [FAIL] [sig-network] LoadBalancers [It] should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow] [sig-network, Slow]
  k8s.io/kubernetes/test/e2e/network/loadbalancer.go:1808
  [FAIL] [sig-network] LoadBalancers [It] should be able to change the type and ports of a TCP service [Slow] [sig-network, Slow]
  k8s.io/kubernetes/test/e2e/network/service.go:454
Ran 442 of 7407 Specs in 1036.153 seconds
FAIL! -- 440 Passed | 2 Failed | 0 Pending | 6965 Skipped

@aojea Could you please help to confirm that is it releated with #124556 ? Thanks.

/retest
let me try it again.

[liangyuanpeng]

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

this should run only on master :/
#124458 (comment)

And kubernetes/test-infra#32539 will resolve it.

[k8s-ci-robot]

@liangyuanpeng: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cadvisor-e2e-kubernetes
• /test pull-kubernetes-conformance-kind-ga-only-parallel
• /test pull-kubernetes-coverage-unit
• /test pull-kubernetes-dependencies
• /test pull-kubernetes-dependencies-go-canary
• /test pull-kubernetes-e2e-gce
• /test pull-kubernetes-e2e-gce-100-performance
• /test pull-kubernetes-e2e-gce-cos
• /test pull-kubernetes-e2e-gce-cos-canary
• /test pull-kubernetes-e2e-gce-cos-no-stage
• /test pull-kubernetes-e2e-gce-network-proxy-http-connect
• /test pull-kubernetes-e2e-kind
• /test pull-kubernetes-e2e-kind-ipv6
• /test pull-kubernetes-integration
• /test pull-kubernetes-integration-go-canary
• /test pull-kubernetes-integration-go-compatibility
• /test pull-kubernetes-kubemark-e2e-gce-scale
• /test pull-kubernetes-node-e2e-containerd
• /test pull-kubernetes-typecheck
• /test pull-kubernetes-unit
• /test pull-kubernetes-unit-go-canary
• /test pull-kubernetes-unit-go-compatibility
• /test pull-kubernetes-update
• /test pull-kubernetes-verify
• /test pull-kubernetes-verify-go-canary

The following commands are available to trigger optional jobs:

• /test check-dependency-stats
• /test pull-e2e-gce-cloud-provider-disabled
• /test pull-kubernetes-apidiff
• /test pull-kubernetes-conformance-kind-ipv6-parallel
• /test pull-kubernetes-cross
• /test pull-kubernetes-e2e-autoscaling-hpa-cm
• /test pull-kubernetes-e2e-autoscaling-hpa-cpu
• /test pull-kubernetes-e2e-autoscaling-vpa-full
• /test pull-kubernetes-e2e-containerd-gce
• /test pull-kubernetes-e2e-gce-canary
• /test pull-kubernetes-e2e-gce-correctness
• /test pull-kubernetes-e2e-gce-device-plugin-gpu
• /test pull-kubernetes-e2e-gce-disruptive-canary
• /test pull-kubernetes-e2e-gce-network-proxy-grpc
• /test pull-kubernetes-e2e-gce-serial
• /test pull-kubernetes-e2e-gce-serial-canary
• /test pull-kubernetes-e2e-gci-gce-autoscaling
• /test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer
• /test pull-kubernetes-e2e-kind-dual-canary
• /test pull-kubernetes-e2e-kind-kms
• /test pull-kubernetes-e2e-kind-multizone
• /test pull-kubernetes-e2e-kind-nftables
• /test pull-kubernetes-e2e-kind-nftables-dual-canary
• /test pull-kubernetes-kubemark-e2e-gce-big
• /test pull-kubernetes-linter-hints
• /test pull-kubernetes-node-arm64-e2e-containerd-ec2
• /test pull-kubernetes-node-arm64-e2e-containerd-serial-ec2
• /test pull-kubernetes-node-arm64-ubuntu-serial-gce
• /test pull-kubernetes-node-e2e-containerd-ec2
• /test pull-kubernetes-node-e2e-containerd-kubetest2
• /test pull-kubernetes-node-e2e-containerd-serial-ec2
• /test pull-kubernetes-node-kubelet-serial-pod-disruption-conditions
• /test pull-kubernetes-verify-lint
• /test pull-publishing-bot-validate

Use /test all to run the following jobs that were automatically triggered:

• pull-kubernetes-conformance-kind-ga-only-parallel
• pull-kubernetes-conformance-kind-ipv6-parallel
• pull-kubernetes-dependencies
• pull-kubernetes-e2e-gce
• pull-kubernetes-e2e-gce-canary
• pull-kubernetes-e2e-kind
• pull-kubernetes-e2e-kind-cloud-provider-loadbalancer
• pull-kubernetes-e2e-kind-ipv6
• pull-kubernetes-integration
• pull-kubernetes-integration-go-compatibility
• pull-kubernetes-linter-hints
• pull-kubernetes-node-e2e-containerd
• pull-kubernetes-typecheck
• pull-kubernetes-unit
• pull-kubernetes-unit-go-compatibility
• pull-kubernetes-verify
• pull-kubernetes-verify-lint

In response to this:

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalance

this should run only on master :/
#124458 (comment)

And kubernetes/test-infra#32539 will resolve it.

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/test-infra repository.

[liangyuanpeng]

pull-kubernetes-e2e-kind-cloud-provider-loadbalancer is only working for master now, so i think it's not the blocker of this PR.

ping @kubernetes/release-managers

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

@liangyuanpeng: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-kind-cloud-provider-loadbalancer	dd08c03	link	false	/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[fedebongio]

/triage accepted