odo devfile push command integration tests (make test-integration-devfile) not work on IBM Z/P

Created on 31 Jul 2020  Â·  14Comments  Â·  Source: openshift/odo

/kind feature

Which functionality do you think we should add?

We are working on odo CI enablement for Z/P. For make test-integration-devfile , most of the tests failed because of error exec format error. The images defined in devfiles.yaml is only for amd64.

Why is this needed?

To enable the tests on IBM P/Z, the default images defined in devfiles.yaml should support s390x or ppcl64le.

areSystem-PZ aretesting kinfeature

All 14 comments

/area system-pz

/area testing

The DefaultDevfileRegistryURL is "https://github.com/odo-devfiles/registry". The devfiles for java-sprintboot is "https://github.com/odo-devfiles/registry/blob/master/devfiles/java-springboot/devfile.yaml" . The container image in this devfile.yaml is quay.io/eclipse/che-java11-maven:nightly ,which only support x86.

Same problem for java-quarkus , the container image used in DefaultDevfileRegistryURL is quay.io/eclipse/che-quarkus:nightly ,which only support x86.

Same problem for java-quarkus , the container image used in DefaultDevfileRegistryURL is quay.io/eclipse/che-java11-maven:nightly,which only support x86.

3578

Till now, I still can not find the replace image which support s390x arch for java devfiles. I found the same discussion about not using personal repo in odo even for testing in #3578 .

The container images used in the default devfile registry of odo doesn't support P and Z. Actually, the images used in default devfile registry is from personal repo and quay.io/eclipse repo. The images also don't support multi-arch. I think the images used in odo should change to use RH offically built images or RH offically registry (registry.access.redhat.com/) like S2I which support multi-arch.

@rgarg1 Is there any plan to support devfiles container image in RH offical registry? Thanks.

@mohammedzee1000 Hope to get your comments, whether or when it is possible to replace container image in devfiles to support P and Z. Thanks

Hi @yselkowitz , Is there any plan to support devfile container images for multi-arch ? The images are quay.io/eclipse/che-quarkus:nightly and quay.io/eclipse/che-java11-maven:nightly and so on in repo quay.io/eclipse/ . Those images are required by odo using devfiles to create applications. Thanks.

@mohammedzee1000 @kadel For your visibility.

This issue is applicable for Power as well.

[odo]  •  Syncing files to the component  ...
[odo] I0929 04:35:20.392962 2111031 adapter.go:198] Creating /test on the remote container if it doesn't already exist
[odo] I0929 04:35:20.392972 2111031 exec.go:27] Executing command [mkdir -p /test] for pod: cnbqwi-6fff88b6cf-v49mq in container: runtime
[odo] time="2020-09-29T08:35:20Z" level=error msg="exec failed: container_linux.go:348: starting container process caused \"exec format error\""
[odo] exec failed: container_linux.go:348: starting container process caused "exec format error"
[odo]  ✗  Syncing files to the component [163ms]
[odo] I0929 04:35:20.556635 2111031 exec.go:43] ExecuteCommand returned an an err: error while streaming command: command terminated with exit code 1. for command '[mkdir -p /test]'. output: time="2020-09-29T08:35:20Z" level=error msg="exec failed: container_linux.go:348: starting container process caused \"exec format error\""
[odo] exec failed: container_linux.go:348: starting container process caused "exec format error"
[odo]  ✗  Failed to start component with name cnbqwi. Error: Failed to create the component: Failed to sync to component with name cnbqwi: failed to sync to component with name cnbqwi: unable to exec command [mkdir -p /test]:
[odo] time="2020-09-29T08:35:20Z" level=error msg="exec failed: container_linux.go:348: starting container process caused \"exec format error\""
[odo] exec failed: container_linux.go:348: starting container process caused "exec format error"
[odo] : error while streaming command: command terminated with exit code 1
Deleting project: cvftlburus

Since the issue have been solved with the private registry . I would like to close this issue and move the discussion to
Duplicate of #4228

Was this page helpful?
0 / 5 - 0 ratings

Related issues

valaparthvi picture valaparthvi  Â·  3Comments

mik-dass picture mik-dass  Â·  7Comments

amitkrout picture amitkrout  Â·  3Comments

anandrkskd picture anandrkskd  Â·  5Comments

prietyc123 picture prietyc123  Â·  3Comments