Description of problem: When VMIO migrates a VM from RHV, it needs to be able to set the disk bus to "scsi" when the source VM is using "virtio_scsi". Currently, the template validation webhook refuses the VM and the following error is returned: "DataVolumeCreationFailed: Error while importing disk image: . admission webhook "virt-template-admission.kubevirt.io" denied the request: virto disk bus type has better performance, install virtio drivers in VM and change bus type: Some of [scsi] are not in [virtio], disk bus has to be either virtio or sata: Some of [scsi] are not in [virtio, sata]". Version-Release number of selected component (if applicable): 2.5.2 How reproducible: Always
Daniel, we would like to target this to 2.6. Will you have the capacity to verify it from V2V side?
It should be aligned with https://bugzilla.redhat.com/show_bug.cgi?id=1903585 We will be able to verify yes
Verification is Blocked by a vmimport crashloopback issue: [amastbau@amastbau totp2]$ oc logs pods/importer-win20191-9de75658-e59b-48db-b7ac-06e79087e98c --follow I0121 10:06:22.930567 1 importer.go:52] Starting importer I0121 10:06:22.931242 1 importer.go:121] begin import process E0121 10:06:24.833751 1 importer.go:137] Fault reason is "Operation Failed". Fault detail is "[Cannot transfer Virtual Disk. The relevant Storage Domain's status is Unknown.]". HTTP response code is "409". HTTP response message is "409 Conflict". Error sending transfer image request kubevirt.io/containerized-data-importer/pkg/importer.getTransfer /remote-source/app/pkg/importer/imageio-datasource.go:272 kubevirt.io/containerized-data-importer/pkg/importer.createImageioReader /remote-source/app/pkg/importer/imageio-datasource.go:184 kubevirt.io/containerized-data-importer/pkg/importer.NewImageioDataSource /remote-source/app/pkg/importer/imageio-datasource.go:60 main.main /remote-source/app/cmd/cdi-importer/importer.go:135 runtime.main /usr/lib/golang/src/runtime/proc.go:203 runtime.goexit /usr/lib/golang/src/runtime/asm_amd64.s:1373 [amastbau@amastbau totp2] will link to BZ once opened
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 2.6.0 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:0799
@Karel, Can this bug be cloned to 2.5.z? Thanks.
It should be technically possible. But I need approve from Kevin or Fabian.
@istein what is the justification for the backport to 2.5.z?
The request to backport this bug to 2.5.z was to allow backporting the v2v bug 1903585, that depends on it. But, I am withdrawing my request since the PM (Miguel Perez Colino) decided to offer update to CNV-2.6, in case the fix for the v2v bug 1903585 is needed.
Thanks Ilanit. There for no backport is needed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days