Bug 1862918 - [v2v] User should only select SRIOV network when importin vm with SRIOV network
Summary: [v2v] User should only select SRIOV network when importin vm with SRIOV network
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Filip Krepinsky
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-03 08:32 UTC by Yaacov Zamir
Modified: 2021-04-04 09:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: imported sriov networks could be set to different network interface type Fix: imported sriov networks are set only to sriov network interface type
Clone Of:
Environment:
Last Closed: 2021-02-24 15:14:01 UTC
Target Upstream Version:
Embargoed:
istein: needinfo+


Attachments (Terms of Use)
screenshot (21.45 KB, image/png)
2020-12-30 11:26 UTC, Ilanit Stein
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github ManageIQ manageiq-v2v-conversion_host pull 82 0 None closed Provide whether network is sriov 2021-02-15 15:55:13 UTC
Github openshift console pull 6495 0 None closed Bug 1862918: add support for import SRIOV networks from oVirt 2021-02-15 15:55:13 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:14:42 UTC

Description Yaacov Zamir 2020-08-03 08:32:53 UTC
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:

Comment 1 Yaacov Zamir 2020-08-03 08:35:16 UTC
@Ilanit FYI

Comment 2 Filip Krepinsky 2020-08-10 15:57:07 UTC
we need a support from backend (kubevirt-vmware) to implement this feature. @Piotr could you take a look at supplying the network interface type?

Comment 3 Piotr Kliczewski 2020-08-10 16:56:31 UTC
@Filip sure, will work on it tomorrow.

Comment 4 Filip Krepinsky 2020-08-10 17:20:01 UTC
Thanks

Comment 5 Filip Krepinsky 2020-08-11 10:39:32 UTC
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

Comment 9 Filip Krepinsky 2020-10-13 10:08:51 UTC
ok so let's retarget this to 4.7 and remove the backport to 4.5

Comment 12 Ilanit Stein 2020-12-30 11:26:08 UTC
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.

Comment 13 Ilanit Stein 2020-12-30 11:26:43 UTC
Created attachment 1743184 [details]
screenshot

Comment 15 errata-xmlrpc 2021-02-24 15:14:01 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 (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


Note You need to log in before you can comment on or make changes to this bug.