DescriptionFelix Dewaleyne
2020-02-17 12:28:38 UTC
Description of problem:
reconfigure doesn't use the default storage type of RHV ; customizations can't change the type of storage either. Cloudforms forces reconfiguration to use virtio when the type should be virtio-scsi. automation trying to pass `"interface" => "virtio_scsi"` don't seem to be honored.
Version-Release number of selected component (if applicable):
cfme-5.10.13+
rhev 4.3.6
rhev 4.3.5
How reproducible:
all the time
Steps to Reproduce:
1.deploy a vm using a templace deploying virtio-scsi
2.go to deployed vm and select "lifecycle > reconfigure"
3.add a storage
Actual results:
storage added is virtio and not virtio-scsi
Expected results:
storage uses the default type in use by rhv, virtio-scsi
Additional info:
virtio lacks features of virtio-scsi that are used by users and cause problems with all matters of automation with new drives, especially BLKDISCARD / UNMAP (TRIM).
the customer is using UNMAP a lot in his day to day operation.
attempts to change the drive added by reconfigure by trying to use the same method used to make cloudforms provision drives as virtio-scsi have no effect : adding to the object `"interface"=>"virtio_scsi"` does not have any effect.
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, 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/RHBA-2020:2020