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

No clear error message is provided if we create a VirtualMachineExport with a nonexistent VM

XMLWordPrintable

    • CNV Storage 275, CNV Storage 276, CNV Storage 277, CNV Storage 278
    • Moderate
    • None

      Description of problem:

      If there is a typo in the VM name while creating the VirtualMachineExport, there is no clear error message provided to the user to point to the problem. The phase of the export will be stuck in "Skipped" state and the status doesn't have much information to understand the problem.

      oc get VirtualMachineExport test-export -o yaml |yq '.status'
conditions:
  - lastProbeTime: null
    lastTransitionTime: "2024-08-29T13:08:58Z"
    reason: VMNoVolumes
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2024-08-29T13:06:43Z"
    reason: Unknown
    status: "False"
    type: PVCReady
links: {}
phase: Skipped
serviceName: virt-export-test-export
tokenSecretRef: secret-test-export
ttlExpirationTime: "2024-08-29T15:06:43Z"
virtualMachineName: test-export

       

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

      OpenShift Virtualization   4.16.1

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create a VirtualMachineExport object with a nonexistent VM:

virtctl vmexport create test-export --vm=test-export

2. Look at the status of the VirtualMachineExport object.

      Actual results:

      No clear error message is provided if we create a VirtualMachineExport with a nonexistent VM

      Expected results:

       

      Additional info:

       

              rh-ee-nassouli Noam Assouline
              rhn-support-nashok Nijin Ashok
              Ahmad Hafi Ahmad Hafi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: