Description of problem:

After adding bundle to index image and adding as a CatalogSource, catalog pod won't start, with the error:

Error: container create failed: time="2020-04-29T03:07:32Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/bin/opm\\\": stat /bin/opm: no such file or directory\"" container_linux.go:349: starting container process caused "exec: \"/bin/opm\": stat /bin/opm: no such file or directory"

Version-Release number of selected component (if applicable):

opm 1.12.1

How reproducible:

Tried multiple times on OCP 4.4 and 4.5 clusters.

Steps to Reproduce:

1. Build and push bundle image using Operator SDK 0.17.0. Image validates fine:

$ operator-sdk bundle validate quay.io/adellape/my-new-operator:v0.1.0

2. Add bundle to new index image:

$ opm index add \
    --bundles quay.io/adellape/my-new-operator:v0.1.0 \
    --tag quay.io/adellape/test-catalog:latest

Completes successfully.

3. Add CatalogSource to OCP cluster (tried on 4.4 and 4.5) referencing index image:

$ cat <<EOF | oc apply -f -

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: test-catalog
  namespace: openshift-marketplace
spec:
  sourceType: grpc
  image: quay.io/adellape/test-catalog:latest
  displayName: Test Catalog
  updateStrategy:
    registryPoll: 
      interval: 30m
EOF

Actual results:

CatalogSource is created and the catalog pod tries to start, however it stays in a ContainerCreateError state with the following error in pod events (from web console):

Error: container create failed: time="2020-04-29T03:07:32Z" level=error msg="container_linux.go:349: starting container process caused \"exec: \\\"/bin/opm\\\": stat /bin/opm: no such file or directory\"" container_linux.go:349: starting container process caused "exec: \"/bin/opm\": stat /bin/opm: no such file or directory"

Expected results:

Catalog loads successfully.

Additional info:

The error seems similar to the one from the already-fixed https://bugzilla.redhat.com/show_bug.cgi?id=1816535, however that one occurred during the `index add` step, and that step completed fine for me.