Description of problem: When a user is willing to import a vm with SROIV network enabled we need to make sure to limit target networks only to SROIVNetworks. JIRA Ref: https://issues.redhat.com/browse/CNV-5821 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
@Ilanit FYI
we need a support from backend (kubevirt-vmware) to implement this feature. @Piotr could you take a look at supplying the network interface type?
@Filip sure, will work on it tomorrow.
Thanks
the fix was merged https://github.com/ManageIQ/manageiq-v2v-conversion_host/pull/82 and @Piotr released a new test image quay.io/pkliczewski/kubevirt-vmware:v2.0.0-6
ok so let's retarget this to 4.7 and remove the backport to 4.5
Verified on: # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-fc.0 True False 7d Cluster version is 4.7.0-fc.0 # oc get csv -n openshift-cnv NAME DISPLAY VERSION REPLACES PHASE kubevirt-hyperconverged-operator.v2.6.0 OpenShift Virtualization 2.6.0 kubevirt-hyperconverged-operator.v2.5.2 Succeeded The network picked for a VM with SRIOV interface imported from RHV was SRIOV. It was not possible to set to a CNV target network other than SRIOV in the VM import wizard. see "screenshot" attached.
Created attachment 1743184 [details] screenshot
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 Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633