Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-174

Failed to install OADP in a disconnected OCP cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • OADP 1.0.0
    • None
    • None
    • None
    • False
    • False
    • Passed
    • 0
    • 0
    • 0
    • Untriaged

      version: OADP 0.5.3, OCP 4.9

      When I create dpa CR in a disconnected OCP, it reported 2 images cannot be pull down. Error as below

       Warning  Failed          31s (x2 over 103s)  kubelet            Failed to pull image "registry.redhat.io/oadp-operator/oadp-registry-container-rhel8@sha256:2574d85059e99332e3f1654ed60949f39e0e115831045250b828dc4ad8601ff2": rpc error: code = Unknown desc = (Mirrors also failed: [ec2-3-129-70-31.us-east-2.compute.amazonaws.com:5000/oadp-operator/oadp-registry-container-rhel8@sha256:2574d85059e99332e3f1654ed60949f39e0e115831045250b828dc4ad8601ff2: reading manifest sha256:2574d85059e99332e3f1654ed60949f39e0e115831045250b828dc4ad8601ff2 in ec2-3-129-70-31.us-east-2.compute.amazonaws.com:5000/oadp-operator/oadp-registry-container-rhel8: manifest unknown: manifest unknown]): registry.redhat.io/oadp-operator/oadp-registry-container-rhel8@sha256:2574d85059e99332e3f1654ed60949f39e0e115831045250b828dc4ad8601ff2: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 23.2.72.86:443: i/o timeout
  Warning  Failed          31s (x2 over 103s)  kubelet            Error: ErrImagePull

      I follow up this doc to install OADP in a disconnected cluster.
      https://docs.google.com/document/d/1mxX4hgEJRgOohYrxW59cG8kBwXkiubH8ts6IiCEYiuw/edit#heading=h.pyna7x30lg3d

      Please notice that when I mirrored images I did pass `--keep-manifest-list=true` as parameter to ensue copy all of manifest into a private registry. The mirror command as below

      $ oc image mirror -a auth.json  --insecure=true --keep-manifest-list=true -f newmapping.txt

      following is the 2 pods that couldn't be pulled down

      $ oc get pod
NAME                                                READY   STATUS                  RESTARTS   AGE
oadp-dpa-sample-1-aws-registry-6cfb488c78-pm52k     0/1     ImagePullBackOff        0          45m
openshift-adp-controller-manager-67858d94d9-ttb8l   1/1     Running                 0          19h
restic-6frcz                                        0/1     Pending                 0          45m
restic-c9887                                        0/1     Pending                 0          45m
restic-mnzsr                                        0/1     Pending                 0          45m
restic-njc2r                                        0/1     Pending                 0          45m
restic-p7fwn                                        0/1     Pending                 0          45m
velero-846b8c977-8s8pp                              0/1     Init:ImagePullBackOff   0          45m

            wnstb Wes Hayutin
            xjiang@redhat.com Xin Jiang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: