Created attachment 1629882 [details]
exec format error in sample code
Description of problem:
Making an 'example' pod which uses the 'hello-openshift' image fails with 'exec format error'
How reproducible: easily
Steps to Reproduce:
1. from the Web Console, create a new workload in the default project with the example 'hello-openshift' application
2. build and run it
runtime fails with 'exec format error'
the example pods run flawlessly
since this is the first thing i would try as a new customer i think we should get the hello-openshift container built for z to not leave a bad first impression, shouldn't be too much effort.
Is this fixed or blocked by the cluster-samples-operator enablement?
Yes, I tested this manually (using a CVO override) with Yaakov's patches several months ago and I was able to run this sample. I believe this is now only blocked by the general incompatibilities of s390x/ppc64le cluster-samples-operator with CI.
Assigning this to Jeremy since Renin is working on a fix.
Bug was reported against 4.2.z, so we should leave that as it stands to show where the breakage starts. Target Release tracks where we want the fix to land, so I'm setting that to 4.6.0. Once the fix lands in master, this bug will get cloned back with Target Release pointing at previous z streams (depending on how far it seems appropriate to backport). The '/cherrypick ...' GitHub/Prow bot will automatically create those backport bugs as needed.
Closing this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1835112.
*** This bug has been marked as a duplicate of bug 1835112 ***
reopening for tracking purposes. still assigned to Jeremy.
Moving to ON_QA since this should be available for 4.6 samples, and is just a test effort.
In OCP 4.5.0-0.nightly-s390x-2020-07-03-213659 on Z
from Administrator->Workloads->Pods->Create Pod
are offered the option of creating a "hello-openshift" sample workload with the yaml:
- name: hello-openshift
- containerPort: 8080
But hitting the "Create" button at the bottom results in a pod that goes into a CrashLoopBackoff state with:
standard_init_linux.go:210: exec user process caused "exec format error"
I'm not quite sure why this would be related to cluster-samples. As noted in comment 3, the image docker.io/openshift/hello-openshift is still only built for amd64, and was not manifest-listed, so this would be the expected result. The only fix for this is for that image to be rebuilt multi-arch, either on docker.io or at some other location (in which case the image: value would have to be modified accordingly).
Yeah, this is not related to cluster samples. My apologies for any confusion my comment caused. I had misunderstood and thought we were discussing one of these templates:
DPTP does not publish this image.
Moving this to console. We can use a different image in the YAML samples.
We're working on adding this image to the release in 4.7 so it supports other architectures.