openshift-install binaries have architecture-specific release payload information embedded therein, meaning that they are not interchangeable even when the install binaries can run on the same architecture. However, particularly with "stable" (non-nightly) releases, it is difficult to tell the release payload architecture from the binary itself: $ ./openshift-install version ./openshift-install 4.9.0-fc.0 built from commit d58fc2b1e982dd1fb07824915c0cbd0a92149d06 release image quay.io/openshift-release-dev/ocp-release@sha256:aecd38724aab2c05045ef526edc2e34a20829c57ecf9085212bc44f25b0845ac Adding a "release architecture" line based on the compile-time default payload architecture could make this easier.
verified. PASS. > amd64 ./openshift-install version ./openshift-install 4.9.0-0.nightly-2021-08-25-185404 built from commit 85e923a636c2253af3dadf0d488241dcd8babb86 release image registry.ci.openshift.org/ocp/release@sha256:e009a8aeae92ae204e207482b118dcfa511325c359a64603285434f37944802f release architecture amd64 > arm64 ./openshift-install version ./openshift-install 4.9.0-0.nightly-arm64-2021-08-25-101342 built from commit 85e923a636c2253af3dadf0d488241dcd8babb86 release image registry.ci.openshift.org/ocp-arm64/release-arm64@sha256:dcbf4365bc7b0a453a415047b90f79eab8b0d34ffb506662bc1c2d74864ac218 release architecture arm64
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759