Bug 2094734

Summary: [RFE] The failure reason is not exposed on VM status if it's failed to import the disk image
Product: Container Native Virtualization (CNV) Reporter: Guohua Ouyang <gouyang>
Component: User ExperienceAssignee: Aviv Turgeman <aturgema>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: low Docs Contact:
Priority: low    
Version: 4.11.0CC: gouyang, tnisan, yzamir
Target Milestone: ---   
Target Release: 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:05:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm_status
none
importer pod log none

Description Guohua Ouyang 2022-06-08 09:09:35 UTC
Created attachment 1887938 [details]
vm_status

Description of problem:
The failure reason is not exposed on VM status if it's failed to import the disk image.
We have this feature in 4.9/4.10, but miss on the new UI.

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


How reproducible:


Steps to Reproduce:
1. create a vm by specify a small disk than the actual disk image
2.
3.

Actual results:
It only show DataVolumeError in vm status

Expected results:
It should expose why the VM is in failed status.

Additional info:

Comment 1 Guohua Ouyang 2022-06-08 09:10:13 UTC
Created attachment 1887940 [details]
importer pod log

Comment 2 Yaacov Zamir 2022-06-15 11:35:10 UTC
We removed this feature to speed the list rendering,
It will be "nice to have" to find a way to restore this feature in a way that does not impact performance.
Adding RFE and moving to low/low to indicate the removal of the feature is by design

Comment 3 Yaacov Zamir 2022-06-15 11:42:14 UTC
Note:

mapping between prinatble statuses and there descriptions can be found here:
https://github.com/kubevirt/kubevirt/blob/298a619ce5ac8015de81fd10b44e32536aac72fb/staging/src/kubevirt.io/api/core/v1/types.go

for example in the case of "DataVolumeError" the description is:
"""
DataVolumeError indicates that an error has been reported by one of the DataVolumes
referenced by the virtual machines.
"""
a link can be provided to the "vm events page" where a user can check for the disks status.

Comment 5 Guohua Ouyang 2023-07-18 09:37:00 UTC
verified on kubevirt-console-plugin-rhel9:v4.14.0-2183, it shows the error from the backend, eg: if for the dataVolumeError, it's 
```
running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
```

Comment 8 errata-xmlrpc 2023-11-08 14:05:03 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 (Important: OpenShift Virtualization 4.14.0 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-2023:6817