Failed to run "post-kubernetes-push-image-etcd"

[kkkkun]

What happened?

Failed to run post-kubernetes-push-image-etcd .
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-kubernetes-push-image-etcd/1649533793343639552

Is it expect? Should we make arm etcd image?

What did you expect to happen?

post-kubernetes-push-image-etcd runs successfully.

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

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-kubernetes-push-image-etcd/1649533793343639552

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[xmudrii]

One option that I see is that we completely remove arm-based etcd image which is in line with what we did for Kubernetes. I think it would be as simple as dropping arm from Makefile, but I might be mistaken.

[kkkkun]

One option that I see is that we completely remove arm-based etcd image which is in line with what we did for Kubernetes. I think it would be as simple as dropping arm from Makefile, but I might be mistaken.

Would kubernetes support arm arm64 ppc64le s390x in the futures? Only support amd64 ？

[xmudrii]

@kkkkun Kubernetes already support amd64 arm64 ppc64le s390x. It's only arm that we dropped very recently (#117508).

[kkkkun]

@kkkkun Kubernetes already support amd64 arm64 ppc64le s390x. It's only arm that we dropped very recently (#117508).

Firstly I would commit PR to fix this.

How to trigger post-kubernetes-push-image-etcd which release etcd:3.5.8-0 and etcd:3.5.7-1 for arm64 ppc64le s390x ?

[BenTheElder]

Are we sure arm32 is the reason the build failed?

[pacoxu]

ifeq (arm,arm)
/bin/sh: syntax error: unexpected word (expecting ")")
make[1]: *** [Makefile:133: build] Error 2
make[1]: Leaving directory '/workspace/cluster/images/etcd'
make: *** [Makefile:215: sub-push-image-linux-arm] Error 2
ERROR
ERROR: build step 0 "gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20221007-69e0da97ef" failed: step exited with non-zero status: 2

I prefer to think that #117560 should fix the issue.

[pacoxu]

/priority important-soon

[kkkkun]

Jobs https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/post-kubernetes-push-image-etcd run successfully.

/close