kruise icon indicating copy to clipboard operation
kruise copied to clipboard

[BUG] E2E Test Failed on arm

Open Colvin-Y opened this issue 9 months ago • 2 comments

What happened: I've run test/e2e cases on my mac locally, and I found case in PodProbeMarker failed because it's asts use image centos:6.7 which is not a multi-arch image and can only run on amd. Related code is here: https://github.com/openkruise/kruise/blob/master/test/e2e/framework/pod_probe_marker_util.go#L213

What you expected to happen: I hope that we can do test in local env but not rely on github actions

How to reproduce it (as minimally and precisely as possible): Use a arm based machine and do test ./bin/ginkgo -timeout 90m -v --focus='\[apps\] PodProbeMarker' test/e2e

Anything else we need to know?:

Environment:

  • Kruise version: latet
  • Kubernetes version (use kubectl version):
  • Install details (e.g. helm install args):
  • Others: I found that image centos:7 is a multi-arch version
[kind-kind|default] ➜  ~ docker manifest inspect centos:7
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 529,
         "digest": "sha256:dead07b4d8ed7e29e98de0f4504d87e8880d4347859d839686a31da35a3b532f",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 529,
         "digest": "sha256:6887440ab977f751d6675157b73e42428d8ac05cf244c5d09ba036cc22d40d13",
         "platform": {
            "architecture": "arm",
            "os": "linux",
            "variant": "v7"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 530,
         "digest": "sha256:73f11afcbb50d8bc70eab9f0850b3fa30e61a419bc48cf426e63527d14a8373b",
         "platform": {
            "architecture": "arm64",
            "os": "linux",
            "variant": "v8"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 529,
         "digest": "sha256:8faead07bd1d5fdd17414a1759eae004da5daa9575a846f4730f44dec0f47843",
         "platform": {
            "architecture": "386",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 529,
         "digest": "sha256:b98bfc4a7094a98ed52d49f9558bb15a4cee9854f182d30085d459d4a55d2e03",
         "platform": {
            "architecture": "ppc64le",
            "os": "linux"
         }
      }
   ]
}
[kind-kind|default] ➜  ~ docker manifest inspect centos:6.7
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 529,
         "digest": "sha256:1e0b26e12f3665414214f67ba01cfc08519f28e9055b07e0fb3caf101f59fcb3",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      }
   ]
}

Colvin-Y avatar May 11 '24 09:05 Colvin-Y

If it's a probelm, can I solve it?

Colvin-Y avatar May 11 '24 09:05 Colvin-Y

I think this is a good first issue. Feel free to contribute to it in any way. @Colvin-Y /good-first-issue

ABNER-1 avatar May 14 '24 15:05 ABNER-1