Description of problem: In VirtualMachine status.volumeSnapshotStatuses[*].reason for some volumes types is wrong, for example ConfigMap volumes don't need storage class, but the reason for it's none snapshot state is that it's lacking storage class. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create a virtual machine with ephimeral, configMap (or other none snpashotable disk) 2. check VirtualMachine status.volumeSnapshotStatuses[*].reason 3. Actual results: "Volume type has no StorageClass defined" Expected results: "Snapshots are not supported for [containerDisk/CloudInit ...] volumes" (or a similar mreason) Additional info: list of volume types: https://kubevirt.io/user-guide/virtual_machines/disks_and_volumes/#volumes cloudInitNoCloud not? cloudInitConfigDrive not? persistentVolumeClaim snapshotable? dataVolume snapshotable? ephemeral not? containerDisk not? emptyDisk not? hostDisk not? configMap not? secret not? serviceAccount not? downwardMetrics not?
Adam, This BZ appears to be more storage related than virt. What do you think?
Adam, I've re-assigned this BZ to storage as it appears to fall under that umbrella. Please feel free to re-assign this if you feel this action was in error.
Won't make it in time for 4.8.1. Pushing out.
Hi, Shelly, do we have any update for the bug?
yeah I just tried the new automation in my PR lets see if it will update the link
This should make 4.8.2 once the v4.8.2-15 build lands.
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.2 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:3598