[IBM Z]: Openshift-marketplace pods are in CrashLoopBackOff state

Openshift-marketplace pods are in CrashLoopBackOff state on all the 4.12 versions on IBM Z. This was observed previously here https://issues.redhat.com/browse/OCPBUGS-621

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

Install any Openshift 4.12 versions on s390x

1.Install any Openshift 4.12 versions on s390x

# oc get po -n openshift-marketplace
NAME                                   READY   STATUS             RESTARTS          AGE
certified-operators-cf5wz              0/1     CrashLoopBackOff   226 (4m47s ago)   21h
certified-operators-zcdln              0/1     CrashLoopBackOff   6 (79s ago)       7m17s
community-operators-7b9f2              1/1     Running            0                 21h
marketplace-operator-cf58785df-dr6bk   1/1     Running            1 (21h ago)       21h
redhat-marketplace-trzx4               0/1     CrashLoopBackOff   227 (11s ago)     21h
redhat-marketplace-wzsxb               0/1     CrashLoopBackOff   6 (25s ago)       6m46s
redhat-operators-jzltr                 1/1     Running            0                 3h21m 

# oc -n openshift-marketplace describe po redhat-marketplace-trzx4
Containers:
  registry-server:
    Container ID:  cri-o://f9145d2f96c469c3fb39f517a54fcc24386b441c9896c3f5ebb49ab4c49fbc92
    Image:         registry.redhat.io/redhat/redhat-marketplace-index:v4.11
    Image ID:      registry.redhat.io/redhat/redhat-marketplace-index@sha256:ba5919e442c3c3f1f869e8d7078a8712314df2757e5d2954293e3a92509844b9
    Port:          50051/TCP
    Host Port:     0/TCP
    State:         Waiting
      Reason:      CrashLoopBackOff
    Last State:    Terminated
      Reason:      Error
      Message:     Error: compute digest: compute hash: write tar: open /tmp/cache/cache: permission denied
Usage:
  opm serve <source_path> [flags]Flags:
      --cache-dir string         if set, sync and persist server cache directory
      --cache-only               sync the serve cache and exit without serving
      --debug                    enable debug logging
  -h, --help                     help for serve
  -p, --port string              port number to serve on (default "50051")
  -t, --termination-log string   path to a container termination log file (default "/dev/termination-log")Global Flags:
      --skip-tls-verify   skip TLS certificate verification for container image registries while pulling bundles
      --use-http          use plain HTTP for container image registries while pulling bundles
      Exit Code:    1
      Started:      Wed, 28 Dec 2022 10:21:00 +0100
      Finished:     Wed, 28 Dec 2022 10:21:00 +0100
    Ready:          False
    Restart Count:  227
    Requests:
      cpu:        10m
      memory:     50Mi
    Liveness:     exec [grpc_health_probe -addr=:50051] delay=10s timeout=5s period=10s #success=1 #failure=3
    Readiness:    exec [grpc_health_probe -addr=:50051] delay=5s timeout=5s period=10s #success=1 #failure=3
    Startup:      exec [grpc_health_probe -addr=:50051] delay=0s timeout=1s period=10s #success=1 #failure=15
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-l999z (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-l999z:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
    ConfigMapName:           openshift-service-ca.crt
    ConfigMapOptional:       <nil>
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
                             node-role.kubernetes.io/master=
Tolerations:                 node-role.kubernetes.io/master:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 120s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 120s
Events:
  Type     Reason   Age                    From     Message
  ----     ------   ----                   ----     -------
  Normal   BackOff  70m (x624 over 3h31m)  kubelet  Back-off pulling image "registry.redhat.io/redhat/redhat-marketplace-index:v4.11"
  Warning  BackOff  20s (x5667 over 21h)   kubelet  Back-off restarting failed container

openshift-marketplace pods should not crash and the multi-arch image should be pulled successfully

Similar Issue : https://issues.redhat.com/browse/OCPBUGS-621