Description of problem:
Customer gets errors when building from Dockerfile and pushing image, due to missing OS and Arch
Version-Release number of selected component (if applicable):
Customer is running latest (updated) OCP 4.4.11 running on VSphere 5.5 and other cluster on 5.7
CoreOS 44.81.202007010318-0 (Ootpa) 4.18.0-147.20.1.el8_1.x86_64
Steps to Reproduce:
Build from Dockerfile.
STEP 8: RUN /usr/libexec/s2i/assemble
---> Enabling s2i support in httpd24 image
---> Installing application source
=> sourcing 20-copy-config.sh ...
=> sourcing 40-ssl-certs.sh ...
---> Generating SSL key pair for httpd...
STEP 9: CMD /usr/libexec/s2i/run
STEP 10: COMMIT temp.builder.openshift.io/rusk/httpd-example-1:0c294c4d
time="2020-07-16T14:50:21Z" level=info msg="Image operating system mismatch: image uses \"\", expecting \"linux\""
time="2020-07-16T14:50:21Z" level=info msg="Image architecture mismatch: image uses \"\", expecting \"amd64\""
Getting image source signatures
Successful build without OS/Arch errors.
Also last release notes  claims  should be fixed (also in 4.5)
possibly linked to
This warning can be ignored - it is logged by the subsystem that selects an image from a manifest list, and does not impact the ability of builds to push images to the internal registry. The logging of this at a "warning" level a known issue, and has been addressed in a newer version of the library.
Moving severity of this issue to "low".
Moving the severity back to "high" - the empty arch/OS tags propagate to the image and imagestream tag, which prevents container scanning tools from working.
This can be fixed by bumping the buildah version in openshift/builder to v1.15.1. For backports we should use buildah v1.14.11 once it is released.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.