Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-34133

[2240029] Expired clone token not reported as permanent failure in DV status

XMLWordPrintable

    • Storage Core Sprint 262
    • Medium
    • No

      Description of problem:
      A clone token is never going to become valid again so we can communicate a terminal state in such case.

      Version-Release number of selected component (if applicable):
      CNV 4.13.4 and lower

      How reproducible:
      100%

      Steps to Reproduce:
      1. Create cross namespace clone DV from non existing source PVC
      2. Wait 5~ minutes
      3. Create the source

      Actual results:
      No indication that the DV will never converge

      Expected results:
      Terminal Failed DV phase since token expired

      Additional info:
      One approach is to backport something along the lines of https://github.com/kubevirt/containerized-data-importer/pull/2742
      Since this is no longer a problem in main.

              skagan@redhat.com Shelly Kagan
              akalenyu Alex Kalenyuk
              Yan Du Yan Du
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: