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

DataVolumeError VM status doesn't show when encountering image pull errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • CNV v4.18.0
    • CNV v4.16.0
    • Storage Platform
    • None
    • Quality / Stability / Reliability
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.99.0.rhel9-2064, CNV v4.99.0.rhel9-1096
    • Storage Core Sprint 263, CNV Storage 264, CNV Storage 265
    • Moderate
    • No

      Description of problem:

      DataVolumeError VM status doesn't show when encountering image pull errors

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

      CNV 4.16.0

      How reproducible:

      100%

      Steps to Reproduce:

      1. [test_id:7679]should report an error status when data volume error occurs 2.
3.

      Actual results:

      Fail

      Expected results:

      Pass

      Additional info:

      This is due to the change in https://github.com/kubevirt/containerized-data-importer/pull/3194;
kubevirt only infers DataVolumeError for the "Error" reason, and, since we now added a new one which it's not aware of, the VM status doesn't fire.

              agilboa@redhat.com Arnon Gilboa
              akalenyu Alex Kalenyuk
              Yan Du Yan Du
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: