OSUS pods never start, they crashloop for a short time then are OOMKilled.
    

Reproducible for customer.
    

    1. Set up a disconnected registry
    2. Mirror the OCP releases.
    3. Create OSUS application.
    

OSUS pods do not start.
    

OSUS pods should start.
    

Customer tried resolution described in KCS https://access.redhat.com/solutions/6976534 (re-mirroring the images and repo in different location) but that had no effect.
$ oc get pods -n openshift-update-service
NAME                                      READY   STATUS             RESTARTS      AGE
graph-data-tag-digest                     1/1     Running            0             28s
ocpupdates-56c6477855-dws2b               0/2     Terminating        0             28s
ocpupdates-56c6477855-w2hkw               0/2     OOMKilled          1 (13s ago)   28s
ocpupdates-58858c6d79-2zvn4               0/2     CrashLoopBackOff   1 (5s ago)    22s
ocpupdates-58858c6d79-4qjfp               0/2     CrashLoopBackOff   1 (7s ago)    22s
updateservice-operator-845595ff48-gqp46   1/1     Running            0             13m

Pod spec:
 resources:
      limits:
        cpu: 750m
        memory: 512Mi
      requests:
        cpu: 150m
        memory: 64Mi

Dockerfile used to generate the graph:
$ cat Dockerfile
FROM registry.access.redhat.com/ubi9/ubi:latest

RUN curl -L -o cincinnati-graph-data.tar.gz https://api.openshift.com/api/upgrades_info/graph-data

RUN mkdir -p /var/lib/cincinnati-graph-data && tar xvzf cincinnati-graph-data.tar.gz -C /var/lib/cincinnati-graph-data/ --no-overwrite-dir --no-same-owner

CMD ["/bin/bash", "-c" ,"exec cp -rp /var/lib/cincinnati-graph-data/* /var/lib/cincinnati/graph-data"]

OSUS application:
$ cat osus.app.yaml
apiVersion: updateservice.operator.openshift.io/v1
kind: UpdateService
metadata:
  name: ocupdate
  namespace: openshift-update-service
spec:
  replicas: 2
  releases: reg.example.com:8443/openshift/release
  graphDataImage: reg.example.com:8443/update/graph-data:latest