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

Registry pod crashes with CrashLoopBackOff for some invalid/unavailable parameters

XMLWordPrintable

    • False
    • False
    • ToDo
    • OADP Sprint 215, OADP Sprint 216, OADP Sprint 217, OADP Sprint 218
    • 4
    • 0
    • 0
    • 0
    • Untriaged

      Description of problem:
      Registry pod crashes with CrashLoopBackOff for some invalid/unavailable parameters like unavailable/invalid region/endpoint/secret (haven’t checked all the wrong values in which it happens, could be other scenarios; will update as will find more), however the DPA remains in reconciled state.

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

      How reproducible: Always

      Steps to reproduce:

      • Create DPA with unavailable/invalid region/endpoint/secret (such as invalid secret token).
      • Create DPA without BSL/VSL(noDefaultBackupLocation: true) and create BSL/VSL resource with unavailable/invalid region/endpoint/secret.

      Actual result: Registry pod crashes with CrashLoopBackOff

      Expected result: The operator should recognize those errors (before/after DPA creation) and not create the registry pod. 

            tkaovila@redhat.com Tiger Kaovilai
            mperetz@redhat.com Maya Peretz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: