Bug 1979957 - CDI importer doesn't report AwaitingVDDK like it used to
Summary: CDI importer doesn't report AwaitingVDDK like it used to
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 2.6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.1
Assignee: Adam Litke
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On: 1965181
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-07 13:46 UTC by Fabien Dupont
Modified: 2021-08-24 12:49 UTC (History)
7 users (show)

Fixed In Version: v4.8.1-12
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1965181
Environment:
Last Closed: 2021-08-24 12:49:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 1852 0 None open [release-v1.34] Add "AwaitingVDDK" back to condition reason. 2021-08-05 02:20:44 UTC
Red Hat Product Errata RHSA-2021:3259 0 None None None 2021-08-24 12:49:30 UTC

Description Fabien Dupont 2021-07-07 13:46:07 UTC
+++ This bug was initially created as a clone of Bug #1965181 +++

Description of problem:
In case vddk-init-image is not added to the v2v-vmware configMap, or set bug not accessible, the DataVolume doesn't report "AwaitingVDDK", like it used to on previous CNV versions.

Version-Release number of selected component (if applicable):
CNV-2.6.3-25
MTV-2.0.0 upstream latest May 24 2021.

Additional info:
This is related to Bug 1902028 - [MTV][RFE] Add a "validation" stage to the current VM migration pipeline. 
This last bug propagates the CDI importer DataVolume reported reason to the migration plan custom resource.
and now that the "AwaitingVDDK" is missing no reason is propagated and it is not clear to why the migration plan in not progressing.

--- Additional comment from Yan Du on 2021-07-07 12:27:38 UTC ---

Moving the bug to modified since the PR is merged.

Comment 2 Ilanit Stein 2021-08-18 16:47:42 UTC
Verified on 
DV:
...
status:
  conditions:
  - lastHeartbeatTime: "2021-08-18T16:39:28Z"
    lastTransitionTime: "2021-08-18T16:39:28Z"
    message: waiting for v2v-vmware configmap for VDDK image
    reason: AwaitingVDDK
    status: "False"
    type: Bound
  - lastHeartbeatTime: "2021-08-18T16:39:28Z"
    lastTransitionTime: "2021-08-18T16:39:28Z"
    status: "False"
    type: Ready
  - lastHeartbeatTime: "2021-08-18T16:39:28Z"
    lastTransitionTime: "2021-08-18T16:39:28Z"
    status: "False"
    type: Running
  phase: ImportScheduled
  progress: N/A


MTV Plan CR:
...
    vms:
    - id: vm-26
      name: v2v-rhel7-mini-istein2
      phase: ImportCreated
      pipeline:
      - annotations:
          unit: MB
        description: Transfer disks.
        name: DiskTransfer
        phase: Blocked
        progress:
          completed: 0
          total: 8192
        tasks:
        - annotations:
            unit: MB
          name: '[env-vcenter67-ims-iscsi-netapp-rdu-01b] v2v-rhel7-mini-istein/v2v-rhel7-mini-istein.vmdk'
          phase: Blocked
          progress:
            completed: 0
            total: 8192
          reason: AwaitingVDDK
      - description: Convert image to kubevirt.
        name: ImageConversion
        progress:
          completed: 0
          total: 1
      started: "2021-08-18T16:39:18Z"
  observedGeneration: 1

Comment 3 Ilanit Stein 2021-08-18 16:51:34 UTC
^^ Verified on MTV-2.1.0-52, CNV-4.8.1-18 iib-97626.

Comment 8 errata-xmlrpc 2021-08-24 12:49:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.8.1 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3259


Note You need to log in before you can comment on or make changes to this bug.