The new operator-sdk image downstream is building the binary with the OCP version tag instead of the version that the SDK binary is built from. $ docker run -it --entrypoint=/bin/sh --user 1000:0 registry.build01.ci.openshift.org/ci-op-6qx8ss8d/stable:operator-sdk sh-4.4$ operator-sdk version operator-sdk version: "7ead15f5-dirty", commit: "7ead15f5713d34654270b7c9fb64ecedcd176d8e", kubernetes version: "v1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64" It should be something like this: operator-sdk version "v1.2.0-ocp", commit: "7ead15f5713d34654270b7c9fb64ecedcd176d8e", ...
Fixed by PR https://github.com/openshift/ocp-release-operator-sdk/pull/88 [jesusr@transam ocp-release-operator-sdk{fix-dockerfile-location}]$ docker run -it --entrypoint=/bin/sh --user 1000:0 registry.build01.ci.openshift.org/ci-op-vyrnkhfv/stable:operator-sdk sh-4.4$ operator-sdk version operator-sdk version: "v1.2.0-ocp", commit: "becd14ac2f95e9bf7641687fd947ad3a4df1f658", kubernetes version: "v1.18.8", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64" This will make it easier to know when a user is using a downstream release of SDK and which upstream release it aligns with.
The latest image openshift-enterprise-operator-sdk-container-v4.7.0-202101190702.p0 doesn't have the fix PR. Will test when the latest image ok.
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.7.0 security, bug fix, and enhancement 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-2020:5633