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

BSL has no status. Velero logs BSL as available then unknown.

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • QE - Ack
    • ToDo
    • No
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      Update documentation

      1.0 to 1.1 CRD inconsistency when

      • Velero was installed by tools other than OADP such as helm chart/velero cli
      • MTC was installed
      • ACM backup/restore version uses OADP 1.0 when oadp 1.1 is also installed.

       

      Thread 1 https://coreos.slack.com/archives/C0144ECKUJ0/p1664212156579079?thread_ts=1663932333.665829&cid=C0144ECKUJ0
      Thread 2 https://coreos.slack.com/archives/C0144ECKUJ0/p1664223537672639
      Thread 3 https://coreos.slack.com/archives/C0144ECKUJ0/p1664802820572269

      Common behavior

      • No status updates to bsl object
      • BSL marked available in the log
      • log show 0/0/1 available/unavailable/unknown rightaway

      Possible cause:

      • Status patch call is failing.

            marnold@redhat.com Matthew Arnold
            tkaovila@redhat.com Tiger Kaovilai
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: