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

Registry pod going in crashloopbackoff state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • OADP 1.0.5
    • OADP 1.0.5
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • oadp-registry-container-1.0.5-7, oadp-operator-bundle-container-1.0.5-18
    • Passed
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • No

      Description of problem:

      Installed OADP 1.0.5 from OLM, noticed a lot of failures on regression tests after analyzing the result we found that there is some issue with registry pod.

      Registry pod going in crashloopbackoff/error state.

       

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

       

      How reproducible:

      Always

       

      Steps to Reproduce:
      1. Create a DPA CR
      2. Check the registry pod status

      Actual results:

      Registry pod is going in crashloopbackoff state.

      $ oc logs oadp-example-velero-1-aws-registry-d549d7778-vskv4
      cp: cannot create regular file '/target/.': No such file or directory
      $ oc get bsl  NAME               PHASE       LAST VALIDATED   AGE   DEFAULT example-velero-1   Available   58s              23m   true
      $ oc get pods 
      NAME                                                 READY   STATUS    RESTARTS      AGE
      oadp-example-velero-1-aws-registry-d549d7778-sjvkm   0/1     Error     2 (26s ago)   30s
      openshift-adp-controller-manager-9b8bd446f-44qdj     1/1     Running   0             13m
      restic-45hbx                                         1/1     Running   0             30s
      restic-drv6j                                         1/1     Running   0             30s
      restic-h4547                                         1/1     Running   0             30s
      velero-65b84d774c-b8z46                              1/1     Running   0             30s

      Expected results:

      Registry pod should not go in crashloopbackoff/error state.

      Additional info:

      Registry pod is working fine in OADP 1.0.4

      $ oc get pods 
      NAME READY STATUS RESTARTS AGE
      oadp-example-velero-1-aws-registry-789b9598f7-gp4cr 1/1 Running 0 9m24s
      openshift-adp-controller-manager-787f4848ff-8psbx 1/1 Running 0 11m
      restic-dv7mw 1/1 Running 0 9m24s
      restic-nh675 1/1 Running 0 9m24s
      restic-rf6jw 1/1 Running 0 9m24s
      velero-556485d6cd-5zr52

              rjohnson@redhat.com Rayford Johnson
              rhn-support-prajoshi Prasad Joshi
              Prasad Joshi Prasad Joshi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: